Crossprobe
MCP server Set up the MCP server

Set up the MCP server

Have the AI assistant you already use build a board, or ask it about one you have. Crossprobe's MCP server gives Claude Code, Claude Desktop, Cursor and other MCP clients the tools to turn requirements into a placed and routed KiCad project, and to read and change an existing one: parts, nets, the ERC, DRC and parity results, the routing, and a picture of the board.

Updated 15 Nov 2026. 3 min read.

What you can do with it

  • Build a board from requirements. Say what the board should do. The assistant picks the circuit, and the server draws the schematic, places and routes the board and runs the checks. You get a KiCad project.
  • Ask about a design. Parts, nets, check results and routing, looked up before the assistant answers.
  • Review a design with the same review as Crossprobe's AI review.
  • Change a design: fields, no-connect flags, moving a part. See Tools and edits.

Two ways to connect

Hosted server Local server (this page)
Install Nothing Node.js 20 or later; KiCad for building boards
Works on Projects stored in your Crossprobe account A KiCad project folder on your disk
A change is saved As a new revision in your account To your files, after you approve, with a backup
Cost One board build a day free; more with a plan Free

Use the hosted server to build a board and open it in the browser with nothing to set up. Use the local server for a project that lives on your disk, next to KiCad. The rest of this page sets up the local one; The hosted server has its own page.

Install

The server is the npm package @crossprobe/mcp (Apache-2.0). There is nothing to install by hand: your MCP client starts it with npx, which downloads it the first time and keeps it cached. You need Node.js 20 or later. To check that it runs:

npx -y @crossprobe/mcp --version

Connect your assistant

The server takes one argument: the KiCad project, as its folder or its .kicad_pro file. Without one, it uses the folder it was started in. You can also leave it out and tell the assistant which project to open.

Claude Code

In a terminal, in your project's folder:

claude mcp add crossprobe -- npx -y @crossprobe/mcp .

Start claude in that folder, and /mcp shows the server and its tools.

Claude Desktop

Open Settings › Developer › Edit Config and add the server to claude_desktop_config.json. Give the project as a full path. Then restart Claude Desktop.

{
  "mcpServers": {
    "crossprobe": {
      "command": "npx",
      "args": ["-y", "@crossprobe/mcp", "/Users/you/kicad/my-board"]
    }
  }
}

Cursor and other MCP clients

The same command works everywhere. In Cursor, put the JSON above in .cursor/mcp.json in your workspace (or in ~/.cursor/mcp.json for all workspaces). Other clients take a command and arguments in their MCP settings.

npx -y @crossprobe/mcp always runs the latest version. To stay on one, name it: @crossprobe/mcp@0.1.0.

What to ask

To have a board built, describe it: "a USB-C powered ESP32-C3 board with an I2C connector and a status LED, 45 × 35 mm". Build a board from requirements shows what happens next. Building needs version 0.2.0 or later of the package, and KiCad installed for its libraries.

Ask about a design in your own words. The assistant looks things up with the tools before it answers. For example:

  • "Which ICs have no decoupling capacitor on their supply pins?"
  • "What's connected to the I²C bus, and does it have pull-ups?"
  • "Triage the DRC results: which ones matter?"
  • "Does every connector pin have a net, or a no-connect flag?"
  • "List the parts without a footprint, and suggest one for each."

For a full review, use the server's design_review prompt (in Claude Code: /mcp__crossprobe__design_review). It runs the same review as Crossprobe's AI review: power, decoupling, pins, connectivity, parts, the PCB, and a triage of the automatic checks. You can give it a scope (schematic, PCB or both) and a focus, such as "runs from a 2S Li-ion pack; check the USB-C input".

The server reads the project again whenever a file changed, so after you save in KiCad, the next answer is about the design as it is now.

Next: Build a board from requirements. Tools and edits lists what the server can look up and change, and Privacy and troubleshooting covers what leaves your computer and what to do when something doesn't work.