HeyPCB for AI agents · MCP server · In beta

A PCB engineer, inside your agent.

Design PCBs from your coding agent. HeyPCB’s engine does the placement, routing and checks; your agent just asks.

Claude Code

claude mcp add --transport http heypcb https://api.heypcb.ai/mcp

Then type /mcp in Claude Code to sign in. Codex, Cursor or Claude?

One address, every client.

One server, the same in every client. Each one signs in with your heypcb.ai account the first time it connects.

01
Add the server. It runs on HeyPCB; there is nothing to install.
Terminal
```
claude mcp add --transport http heypcb https://api.heypcb.ai/mcp
```
02
In Claude Code, type /mcp, pick heypcb and sign in with your heypcb.ai account in the browser that opens.

In every project

The command above adds HeyPCB to the project you are in. This one adds it everywhere:

Terminal

claude mcp add --scope user --transport http heypcb https://api.heypcb.ai/mcp

Or run it on your computer

The local server, @heypcb/mcp, talks to the same server and adds two tools that use your disk: it uploads a KiCad folder as a project and saves exports to a folder. It needs Node.js. Sign in once with the second command, or set HEYPCB_API_KEY to a personal key.

Terminal

claude mcp add heypcb -- npx -y @heypcb/mcp

Terminal · sign in once

npx @heypcb/mcp login

01
Add the server to Codex’s config file.
~/.codex/config.toml
```
[mcp_servers.heypcb]
url = "https://api.heypcb.ai/mcp"
```
02
Sign in: run this and sign in with your heypcb.ai account in the browser that opens.
Terminal
```
codex mcp login heypcb
```

Or from the terminal

This writes the same lines into the config file for you. Then sign in as above.

Terminal

codex mcp add heypcb --url https://api.heypcb.ai/mcp

01
With Cursor installed, this button opens it and asks you to confirm the server.
Add to Cursor
02
When Cursor connects to heypcb for the first time, sign in with your heypcb.ai account in the browser that opens.

Or by hand

Put this in .cursor/mcp.json in your project, or in ~/.cursor/mcp.json for every project.

.cursor/mcp.json

{
  "mcpServers": {
    "heypcb": {
      "url": "https://api.heypcb.ai/mcp"
    }
  }
}

01
In claude.ai or the Claude desktop app, open Settings → Connectors and choose Add custom connector. Name it HeyPCB, paste this address and press Add.
Remote MCP server URL
```
https://api.heypcb.ai/mcp
```
02
Press Connect beside HeyPCB and sign in with your heypcb.ai account in the browser that opens.
03
In a chat, turn HeyPCB on from the + menu, then ask for a board.

01
Give your client this address. It speaks MCP over Streamable HTTP.
Server URL · Streamable HTTP
```
https://api.heypcb.ai/mcp
```
02
It signs in with OAuth 2.1 and PKCE. A client that registers itself finds everything it needs from the address alone; you sign in with your heypcb.ai account in the browser that opens. A client that takes only a header can send a personal key instead, as Authorization: Bearer hpcb_pk_…. Make one in Settings → Devices & API keys.

A client that runs servers on your computer

Run the local server with npx and a personal key, in the mcpServers shape most clients read.

JSON config

{
  "mcpServers": {
    "heypcb": {
      "command": "npx",
      "args": [
        "-y",
        "@heypcb/mcp"
      ],
      "env": {
        "HEYPCB_API_KEY": "hpcb_pk_…"
      }
    }
  }
}

What your agent can do.

A few tools that each do a whole job, so your agent asks for a board instead of editing KiCad files. Paste a prompt to try one.

01
Build a board from a brief.
Inky takes a plain-language brief to a finished board: the schematic, the parts, placement, routing and the checks. It keeps going until the board is done or it needs your decision.
build_board · wait_for_turn
Prompt
```
Use HeyPCB to design a USB-C powered ESP32 sensor board with a BME280, then export Gerbers.
```
02
Ask Inky.
A question about a board, or an edit in plain words. When Inky needs a decision, such as approving a plan, your agent brings the question back to you.
ask_inky · answer_decision
Prompt
```
Ask Inky on my HeyPCB board whether every chip has a decoupling capacitor, and add any that are missing.
```
03
Check it.
DRC and ERC, Inky's full verification, or the fab-readiness check, with every finding listed.
check_board
Prompt
```
Run HeyPCB's fab-readiness check on my latest board and list anything that would stop an order.
```
04
Route it.
An autorouting job on HeyPCB's engine. Your agent waits for it and gets the result.
route_board
Prompt
```
Route my HeyPCB board, then tell me how many connections are still open.
```
05
Place the parts.
The engine places the board's parts again.
place_parts
Prompt
```
Re-place the parts on my HeyPCB board, then show me the top side.
```
06
See the board.
The board's facts (size, layers, parts, nets, how much is routed, DRC and ERC counts) and a picture of the top, the bottom, the schematic or the 3D view.
get_board · get_board_image
Prompt
```
Show me the top of my HeyPCB board and its schematic, and tell me how big it is.
```
07
Export the files.
Gerbers, the KiCad project, the BOM, the CPL or a STEP model, as a short-lived download link.
export
Prompt
```
Export Gerbers, the BOM and a STEP model of my HeyPCB board.
```
08
Bring your own KiCad project.
Local server
A KiCad folder on your computer becomes a HeyPCB project, and exports save straight to your disk.
upload_kicad_project · save_export
Prompt
```
Upload the KiCad project in ./hardware to HeyPCB and run DRC and ERC on it.
```

Every board is a real board.

01
A board you can open.
Every board your agent makes is a project in your heypcb.ai account. The tools answer with its address, so you can open it, look at it and edit it by hand beside Inky.
02
Real KiCad files.
The board is a KiCad project, checked by KiCad's own DRC and ERC. Export it, or the Gerbers, BOM, CPL and STEP a board house takes.
03
Your decisions stay yours.
When Inky needs a decision, such as approving a plan or routing now, your agent brings the question back to you. Undo puts the board back.

One account.

The MCP server uses your heypcb.ai account and its balance. Inky’s turns, which build and edit the board, cost what they cost on heypcb.ai. Engine runs are priced per run, and your agent can ask for the price before it starts one.

Route the boardroute_board: $0.10 plus $0.001 a pad, at most $1.00
Place the partsplace_parts: $0.05
Verify the boardcheck_board: $0.05
Fab-readiness checkcheck_board: $0.05
DRC or ERCcheck_board: $0.02 each
Board facts, pictures, exports, estimates and undoget_board · get_board_image · export · estimate · undo: Free

In beta.

The MCP server signs in only for accounts on the beta list for now; any other account is told so when it signs in. It is the same account, balance and boards as heypcb.ai and HeyPCB for KiCad.

Create a heypcb.ai account Working in KiCad? Get HeyPCB for KiCad

One address, every client.

In every project

Or run it on your computer

Or from the terminal

Or by hand

A client that runs servers on your computer

What your agent can do.

Build a board from a brief.

Ask Inky.

Check it.

Route it.

Place the parts.

See the board.

Export the files.

Bring your own KiCad project.

Every board is a real board.

A board you can open.

Real KiCad files.

Your decisions stay yours.

One account.

In beta.