HeyPCB MCP
The HeyPCB MCP server: an agent designs KiCad printed circuit boards, picks parts, routes and runs DRC before release.
- 60 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Paid operations are charged from the HeyPCB wallet and the server does not yet enforce a spend limit
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/heypcb-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Paid operations are charged from the HeyPCB wallet and the server does not yet enforce a spend limit
This is third-party code. Review the repository files before installing.
What it does
HeyPCB MCP connects Claude Code, Codex, Cursor or Claude Desktop to the HeyPCB service. There are two ways to work. In the first the agent sets a task with one `build_board` call and the server-side designer Inky picks parts, places, routes and runs checks. In the second the agent builds the board itself with `search_parts`, `add_block`, `connect`, `move_part` and `add_ground_pour`. The `check_board` call returns DRC and ERC findings, each naming a fixing call as `fixWith`. A finished board is exported as Gerber, BOM, pick-and-place and STEP. The local server in the `@heypcb/mcp` package additionally opens a KiCad project in its own folder, syncs edits back and runs the stock `kicad-cli` checks offline.
Who it is for. Electronics developers and hobbyists who describe a device in words and want a KiCad board ready to order from a fab.
Good fit when
- A board on an ATtiny85 with USB-C power is needed and you describe it in text
- An agent adds a regulator to a microcontroller and wires it to the right nets
- DRC and ERC must be checked on an existing KiCad project without going online
- Before ordering a board you need Gerber, BOM and pick-and-place as one set
Not a fit when
- Spending from a HeyPCB wallet is not acceptable, since seven tools run paid server work
- A board is needed without access to an outside service and local KiCad checks are not enough
- Hand tuning of complex high-frequency routing is needed without an agent
Example request
Build a board on an ATtiny85 with USB-C power, show the cost estimate before running and verify the result with `check_board`.MCP
- Transport
- http, stdio
- Authentication
- OAuth
Limitations
Design runs through a HeyPCB account: OAuth sign-in in the browser, and paid operations are charged from the wallet at heypcb.ai rates. The paid tools are `build_board`, `ask_inky`, `answer_decision`, `check_board`, `route_board`, `place_parts` and `preview_placement`, and `estimate` shows the price first. The server does not yet enforce spend limits via `--max-spend`, so paid calls are refused when a cap is set. Codex cannot sign in to the remote server and needs the local package with Node.js 18 or newer.
How to disable. Remove the server with `claude mcp remove heypcb` or delete the entry from the client settings. Account access is revoked on heypcb.ai.
FAQ
Remote or local server?
The remote one needs no installation and suits Claude Code. The local one is for Codex, working with a KiCad project in its own folder and offline checks.
How much does it cost?
The same as on heypcb.ai, from the same wallet. `estimate` shows an operation price before running and `whoami` shows the balance.
How do I verify a board before manufacturing?
`check_board` runs DRC, ERC and the placement check, and each finding includes a `fixWith` call to repair it.
Can an agent edit be rolled back?
Yes. `list_history`, `restore_board` and `redo` return the board to an earlier state, and an edit is applied as one undoable change.
What do I get as output?
Gerber, a KiCad project, BOM, pick-and-place and STEP through a short-lived link from `export`, while the local server saves files to a folder.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server for PCB design in KiCAD: the agent places components, routes connections, runs DRC and prepares manufacturing files
MCP server for PCB design in KiCAD 10: schematic, routing, checks and manufacturing prep through an agent
MCP 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.
Component search for PCB assembly: parametric filters, JLCPCB, Mouser and DigiKey stock and prices, KiCad files
Altium MCP Server gives Claude access to an open Altium Designer project: board queries, symbols, footprints and output jobs
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| HeyPCB MCP (this card) | yes | OAuth | 60 | |
| KiCAD MCP Server | no | not required | 3,285 | works with a local KiCad project; HeyPCB MCP also designs the whole board on the service side |
| PCB Parts MCP Server | no | not required | 146 | searches parts; HeyPCB MCP adds placement, routing, DRC and fab export |
README in short
The remote and local modes give the same design tools, and the local one adds work with a KiCad project folder. Every paid call can be priced in advance.