KiCAD MCP Server
An MCP server for PCB design in KiCAD: the agent places components, routes connections, runs DRC and prepares manufacturing files
- 3,285 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Creates and modifies KiCAD project files and exports manufacturing files
- Launches external processes such as Freerouting via Java or Docker and calls APIs with keys
Install
- Works in
Manual install
git clone https://github.com/mixelpixx/KiCAD-MCP-Server.git
cd KiCAD-MCP-Server
npm install
npm run buildBuild from source. Requires KiCAD 9.0+, Node.js 18+ and Python 3.11+.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Creates and modifies KiCAD project files and exports manufacturing files
- Launches external processes such as Freerouting via Java or Docker and calls APIs with keys
This is third-party code. Review the repository files before installing.
What it does
The server links an agent such as Claude with KiCAD and lets you work on a board in natural language. Through a set of tools the agent creates a project, edits the schematic, places components, routes connections, runs DRC and ERC checks and exports manufacturing files. There is separate support for creating custom symbols and footprints for parts outside the standard library and keeping a personal library for reuse. It integrates the JLCPCB catalog with pricing and stock and automatic routing via Freerouting on Java or Docker. The server is built on the MCP specification and runs on Windows, Linux and macOS, requiring an installed KiCAD.
Who it is for. For engineers and electronics hobbyists who design PCBs in KiCAD and want to run part of the work through an agent.
Good fit when
- You need to create or edit a KiCAD board project from an agent
- You need to create a custom symbol or footprint for a non-standard part
- You need to run DRC and ERC checks or prepare a manufacturing export
Not a fit when
- KiCAD 9.0+ is not installed, or Node.js and Python for the build are missing
- The result goes into a critical application without mandatory human engineering review
Example request
Create a new KiCAD board project, place these components and run a DRC checkMCP
- Transport
- stdio
- Authentication
- not required
Environment variables
PYTHONPATH- Path to the Python from the KiCAD install; auto-detected when a venv exists.
JLCPCB_API_KEYsecret- JLCPCB key for real-time part lookup; without it a local database is used.
DIGIKEY_CLIENT_SECRETsecret- Digi-Key app secret for part lookup, set in the .env file.
Limitations
The server installs by building from source: it needs KiCAD 9.0+, Node.js 18+ and Python 3.11+, and after cloning you run npm install and npm run build, then register the server in the client configuration as a local node command. Some features need external pieces: Freerouting runs via Java or Docker, and JLCPCB and Digi-Key part lookup connect through API keys set in a .env file. The authors warn that design suggestions do not replace engineering review and that critical applications require independent expert verification. The README also mentions a Rust successor, Konnect, for KiCAD 10 under a different license, but this server stays open under MIT and maintained.
How to disable. Remove the kicad entry from the mcpServers block in the client configuration, for example in claude_desktop_config.json, and delete the folder with the built server.
FAQ
Do I need a separate key to use it?
Working with KiCAD itself needs no keys. API keys are only required for JLCPCB and Digi-Key part lookup and are set in a .env file; without them lookup uses a local database.
How does it differ from Konnect?
Konnect is a from-scratch Rust successor for KiCAD 10 under a different license. This Python and TypeScript server stays open under MIT and maintained.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server for KiCad: schematics, PCBs, ERC and DRC checks, DFM and manufacturing prep from an agent
Seeed Studio's MCP server reads KiCad schematics and boards, traces pin-level connections and runs ERC and DRC through kicad-cli.
MCP server for PCB design in KiCAD 10: schematic, routing, checks and manufacturing prep through an agent
The HeyPCB MCP server: an agent designs KiCad printed circuit boards, picks parts, routes and runs DRC before release.
Component search for PCB assembly: parametric filters, JLCPCB, Mouser and DigiKey stock and prices, KiCad files
The kct CLI and a Python library for agents: parse and edit KiCad schematics and PCBs with JSON output, run DRC and ERC without a running KiCad
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| KiCAD MCP Server (this card) | no | not required | 3,285 | |
| copperhead | no | 694 | a CLI agent for circuit boards | |
| eda-agent | no | not required | 349 | an MCP server that lets an agent edit an open project in Altium |
README in short
The README presents KiCAD MCP Server as a Model Context Protocol server that lets agents such as Claude work with KiCAD for PCB design. It lists project setup, schematic editing, component placement, routing, DRC and ERC checks and export, plus creating custom symbols and footprints and keeping a personal library. It integrates the JLCPCB catalog and Freerouting automatic routing, with snapshots and session logs for traceability. Installation is by cloning and building with npm, then configuring the client, with example configs for GitHub Copilot in VS Code and Claude Desktop. The README includes a disclaimer of no warranty and the need for engineering review. MIT licensed.