KiCad and AI: what actually works
KiCad has no built-in AI. What exists is an ecosystem around it — MCP servers, plugins, scripts — plus a separate class of AI-native tools. Here is an honest map of the options and what each is genuinely good for.
One thing worth fixing in your head before comparing any of these: when an AI triggers KiCad’s autorouter, KiCad routes the board. The model supplied the intent and the sequence. That distinction decides which of the approaches below can actually help you, and with what.
1.MCP servers — let an AI agent drive KiCad
The Model Context Protocol lets an assistant call tools directly. Open-source community MCP servers for KiCad expose schematic, board, ERC/DRC, BOM and export operations as callable tools, so Claude, Cursor, Copilot or any MCP client can operate KiCad programmatically rather than by clicking.
This is the most capable approach available today, and it is genuinely powerful for repetitive or scripted work: batch edits, running checks, generating BOMs, driving exports, reviewing a design against rules.
It is a developer setup. You install a server, wire it to your assistant, and keep it working across KiCad versions. And the agent is still calling KiCad's engines — the routing quality is KiCad's, not the model's.
2.Python scripting with an assistant's help
KiCad has had a Python API for years. An assistant is very good at writing those scripts: bulk-renaming nets, generating footprints, pulling data out of a board file, automating a repetitive edit you would otherwise do a hundred times by hand.
Lowest friction, no new infrastructure, and completely deterministic once the script exists. For most people this is the highest-value AI-and-KiCad combination and it is badly underrated.
You need to read and test what the assistant writes. A script that silently mangles a board file is worse than no script, so run it on a copy first.
3.Computer use — a model clicking the KiCad GUI
Newer models can operate a desktop application directly: open KiCad, place parts, press Auto-Route, export. It is real, and it demos well.
Nothing to install and no API to learn. Useful for exploring what an agent can do, and for one-off tasks where writing a script is not worth it.
It is the slowest path — every action costs a screenshot, a decision and a click, for work KiCad's own scripting interface does in milliseconds. It is also not reproducible: run it twice and the model may take a different route and land on a different board.
4.AI-native tools that are not KiCad
A separate class of tool generates the design itself — you describe a board and get it wired, placed and routed, with Gerbers to export.
Nothing to set up, and it covers the step the other approaches do not: producing a design from intent rather than automating edits to one you already have.
It is a different tool, not a KiCad add-on. If your workflow, libraries and team are built around KiCad, an MCP server or a script keeps you where you are.
KiCad AI plugins and MCP servers you can install
KiCad itself ships no AI: its 10.0 release announcement lists no AI feature and no MCP server. What you can install comes from community projects, either a plugin that adds an AI chat to KiCad’s own editors or an MCP server that lets the assistant you already use drive KiCad; whichever you try, check the KiCad version it supports, run it on a copy of your project first and run DRC after every AI edit, because these projects change quickly.
For a hosted PCB MCP server side by side with Altium and Flux (install, routing, checks, file formats and cost), see MCP servers for PCB design compared.
AI placement and routing in KiCad
The two searches people make most after “KiCad AI” are placement and the autorouter, and the honest answers are different. For placement, an assistant can move footprints through KiCad’s API and follow rules you give it, but it does not measure clearances as it goes: run DRC after every pass. For routing, KiCad has an interactive router but no autorouter, so automatic routing means the open-source Freerouting, which some MCP servers can trigger. In both cases the AI is operating an engine; the quality comes from the engine and from your review.
If you want the board placed, routed and checked before you see it, that is the job of an AI-native tool such as PCBEditor’s router, which still hands you a KiCad 9 project at the end.
Where AI helps, and where it cannot
Across all four approaches the same line holds. A language model is strong at judgement — which regulator, which topology, what a script should do, which checks to run. It has no way to measure whether a trace clears a pad by 0.15 mm, so everything that depends on measurement has to come from an engine that measures: a router, a rule checker, a geometry library. AI that automates the operating of those engines is useful. AI asked to be one is not.
Why an LLM cannot apply the physics →Common questions
- What is the best KiCad AI plugin?
- It depends on where you want the AI. If you want to chat with it inside KiCad's own editors, an in-editor plugin fits. If you already use Claude, Cursor or another MCP client, a KiCad MCP server lets that assistant drive KiCad. Either way, check which KiCad version the project supports and run DRC yourself after any AI edit.
- Can AI do component placement in KiCad?
- An assistant connected through a plugin or MCP server can move footprints by setting their positions through KiCad's API, and it can follow rules you state, such as connectors on the board edge or decoupling capacitors next to their pins. It does not measure clearances or courtyards as it goes, so run KiCad's DRC after every AI placement pass and treat the result as a first draft.
- Does KiCad have an AI autorouter?
- No. KiCad's interactive router helps you route by hand, and for automatic routing most people export the board to the open-source Freerouting autorouter, directly or through a plugin; some MCP servers wrap that step so an assistant can trigger it. The routing quality is Freerouting's either way, not the model's.
- Can AI generate a KiCad schematic?
- Through an MCP server or plugin, an assistant can add symbols and wires to a KiCad schematic one tool call at a time. Separately, AI-native tools generate the whole schematic from a description: PCBEditor, for example, exports its generated schematics as native .kicad_sch files and its boards as KiCad 9 projects, so you can continue in KiCad.
- Does KiCad have built-in AI?
- No. KiCad has no native AI assistant. Everything described here comes from the ecosystem around it — MCP servers, plugins and scripts built by the community — or from separate AI-native tools used alongside it.
- What is a KiCad MCP server?
- It is a small program that exposes KiCad operations as tools an AI assistant can call through the Model Context Protocol. With one installed, an assistant such as Claude, Cursor or Copilot can create and edit schematics and boards, run ERC and DRC, generate BOMs and drive exports, without you clicking through the GUI. KiCad does not ship one; the implementations are open-source community projects.
- Can Claude, Cursor or Copilot design a PCB in KiCad?
- They can operate KiCad through an MCP server, which means they can perform the actions — place parts, run checks, export files. What they are not doing is routing the board themselves: KiCad's router does that work, and the result is whatever KiCad would have produced. The model supplies intent and sequencing, not copper.
- Does a better model mean better routing?
- No, and it is worth knowing before spending on tokens. Routing is a constrained search over physical space. A model that reasons better does not reduce the number of grid cells a router evaluates, because none of that work is language. Improving the router improves routing; improving the model does not.
- Which approach should I start with?
- If you want a specific repetitive task automated, start with Python scripting and an assistant — it is the least setup for the most reliable payoff. If you want an agent that can work across a whole project, install an MCP server. If what you actually want is a board generated from a description, that is a different kind of tool.
If what you are really after is the fourth option — describe a board and get one placed, routed and checked, with Gerbers at the end and nothing to install — that is what PCBEditor does. If your work lives in KiCad, an MCP server or a script is the better fit, and this page is not trying to talk you out of it.
Try PCBEditor free →