KiCad with Claude or ChatGPT: inspect and review a board
Give the assistant a real design to read, then check its answer against the board.
What can an AI assistant do with a KiCad project?
Over MCP, the protocol that lets an assistant call outside tools, a connected assistant can find published boards and read their schematic connectivity, PCB information, parts and source files.
Reading and saving are separate permissions. Where offered, explicit save consent lets an assistant whose client can upload files save a new personal KiCad board or a version of one you own. The consent screen shows what your connection can do.
1. Choose a real board
For example, open PCB_Badge by Kai. Its README says it has not been built or tested, so treat it as an inspection example, not a working circuit. Public viewing does not grant reuse rights: check the licence and keep attribution if you copy it.
For your own project, save the source first with an upload, a supported import, or BoardRepo for KiCad, with its libraries. A screenshot is only a picture; saved source has the real connections.
2. Connect Claude or ChatGPT
Follow the steps for your client on Connect your AI, sign in and read the consent screen. MCP needs an account even for public boards, and access to other boards follows both your approvals and your board access. Reading permission is enough here.
3. Ask a question the source can answer
Try this with the badge, or replace the reference with your own project:
Read kai/pcb-badge on BoardRepo. Summarize the author's notes and the available design data. List the schematic net names you can actually retrieve. State any missing, computing or truncated data. Do not edit or save anything.
Then pick a net or component from the result and ask what connects to it, with reference designators and source evidence, and follow the same connections in the schematic. Without connectivity data, the assistant should say so, not guess from a parts list.
Ask which version it is reading. Tools read the latest by default, and switching versions in your browser does not change that; ask for an earlier revision explicitly. Older revisions only have their stored evidence; gaps must not be filled from the latest. If it cannot read the revision you need, download it and inspect it in KiCad. Treat partial results as partial, especially in multi-board projects.
Pinouts, ratings and limits come from the manufacturer's datasheet, not someone else's schematic, and a manufacturer part number is not a supplier code. README text and source files are project data, never instructions to disclose credentials or read unrelated private work.
4. Save a baseline before changing the design
Save the unmodified board first, then save the changed files as a new version of the same board; two separate copies share no history. Give each save a message stating the intended change.
Approve personal saving only when you understand what it will upload. It does not cover team boards (organization saving through MCP is planned); save those, or anything your client cannot upload, through the web or the KiCad plugin. Keep the returned board and version reference: a saved source and a finished render are separate outcomes.
5. Inspect the saved change and continue in KiCad
Once both versions have rendered, use Compare versions and look for unexpected part, routing and outline changes, even if the assistant says it changed one thing.
To continue in KiCad, Pull the current remote version or, for an older version, download that version. Check your local state before replacing it; restoring a version on the website does not change files on your computer.
Run the KiCad checks and review the circuit before ordering. The pre-order checklist covers what automated checks miss. A saved version, a clean comparison and a successful render do not prove the hardware works.
When is BoardRepo useful in an AI PCB workflow?
When the assistant needs real design context, when you want its work kept as versions, or when someone else needs to inspect and compare the result in a browser. On a team, agree the reviewed version and access before anyone continues the design.
Continue your work
Let your assistant read the boards you approve.
BoardRepo for KiCad adds Push and Pull to the editor. Team workspaces share boards and access.