Crossprobe
MCP server Connect your assistant

Connect your assistant

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 the projects stored in your account. There is nothing to install.

Updated 22 Nov 2026. 5 min read.

Runs On Crossprobe's servers. Your assistant connects to it over HTTPS
Works on The projects stored in your account, and new ones it builds there
Needs A Crossprobe account. You sign in when your assistant asks. Nothing to install
Also A read-only local server for a project on your disk
Saves Every change as a new revision. Earlier revisions are kept
Costs One board build a day for free; more with the Connect plan

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. The result is a KiCad project in your account.
  • Ask about a design. Parts, nets, the ERC, DRC and parity results, the routing, and a picture of the board or a schematic sheet, looked up before the assistant answers.
  • Review a design with the server's review prompt: power, decoupling, pins, connectivity, parts and the PCB.
  • Change a design: fields, no-connect flags, moving a part. See Tools and edits.

Connect an assistant

Give your assistant the server's address. The first time it connects, it opens Crossprobe in your browser: sign in, check which assistant is asking, and choose Allow. There is no token to copy.

Assistant What to do
Claude Code Run claude mcp add --transport http crossprobe https://crossprobe.ai/mcp, then type /mcp in Claude Code and sign in
Claude (web and desktop) In Settings → Connectors, add a custom connector with the address https://crossprobe.ai/mcp, then choose Connect
ChatGPT In Settings, turn on developer mode, then add a connector with the address and OAuth
Cursor Add a crossprobe entry with the address to ~/.cursor/mcp.json; Cursor asks you to sign in
VS Code (Copilot) Add a crossprobe server of type http with the address to .vscode/mcp.json; VS Code asks you to sign in
Other clients The address, which ends in /mcp. A client that supports OAuth for MCP finds the sign-in by itself

Connect MCP in the app gives the same setups, with the address filled in.

Each assistant you allow is listed under Connect an assistant… in the account menu, and you can disconnect it there. Your assistant keeps its sign-in by itself; you sign in again only if you disconnect it or it goes unused for a long time.

With an access token instead

For a client that can't sign in by itself, or for a script, make an access token:

  1. Open Crossprobe, sign in and choose Connect MCP.
  2. Choose Use an access token instead, give the token a name that says what it is for, such as "CI script", and make it.
  3. Copy what the tab shows, with the token filled in: the address with an Authorization: Bearer header, or, for a client that takes only an address, the address with the token in it. The token is shown once.

A token lets its holder read and change your stored projects, so treat it like a password. You can have up to ten, and revoke any of them in the same place. Only a fingerprint of a token is kept on the server.

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.

To work on a project you already have, store it in your account first. Then ask in your own words, starting with "list my Crossprobe projects". 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 takes the assistant through a whole 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".

Saving

The assistant saves without asking first. A proposal that isn't saved doesn't show in the app, and is gone after a day, so waiting would only leave you looking at nothing.

Nothing is lost by it:

  • Each save is a new revision of the project. The last 50 are kept, and you can open any of them from the project menu.
  • A revision made by an assistant is marked as such, with its reason.
  • Nothing is deleted through the server.

If the project is open in the app when an assistant saves, the app tells you the next time its tab gets focus and offers to load the new revision. If you have unsaved changes of your own, it keeps them and lets you choose.

When the same design is built again, it is saved as a new revision of the same project, not as another project.

To work on the result in KiCad, download the project from the app: it is plain KiCad files.

What it costs

A board build is what takes computing: placing and routing a board, or routing again after a part is moved.

Board builds a day Stored projects
Free 1 3 private; shared publicly, no fixed limit
Connect, €4.90 a month 100 No fixed limit (fair use)
  • A build counts when it has built something. A spec that is sent back with mistakes to correct does not.
  • Reading a project, pictures of it, and saving are not counted as builds.
  • The count starts again at 00:00 UTC.
  • When the day's builds are used, the assistant is told so and tells you. What it already built can still be looked at and saved.
  • A build is stopped after 150 seconds.

Connect is for designing with your own assistant: the model that does the thinking is the one you already pay for, and the plan pays for building the boards and keeping your projects. You subscribe in the app, under Plans and usage… in the account menu. See Plans and usage, which also has the fair-use terms for storage.

A project on your own disk

If the project lives on your disk and you only want to ask about it, there is also a local server: it reads a KiCad project folder, writes nothing, and needs no account. Building a board and changing a design are done here, on the hosted server.

Privacy

Your stored projects are kept in Crossprobe's storage in the EU, private to your account. The server reads them there. Your assistant's model sees what the tools return when it asks: a part, a net, a list of check results, a picture. It never gets your files as a whole, and where that model runs is up to your assistant. See Privacy and data.

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