Crossprobe
MCP server Privacy and troubleshooting

Privacy and troubleshooting

The local server sends nothing anywhere: it reads your project from disk and answers your MCP client. The hosted server works on the projects stored in your account. Below, fixes for the problems you are most likely to meet with either.

Updated 15 Nov 2026. 3 min read.

What leaves your computer

The local server itself sends nothing anywhere: it reads your project from disk and answers your MCP client. The client's model sees what the tools return when it asks: for example a part's pins, a net, or a list of check results. It never gets your files as a whole. Where that model runs is up to your client and its settings.

With the hosted server the projects are the ones you stored in your Crossprobe account, and the server reads them there. The model again sees only what the tools return.

Troubleshooting

The local server

  • The server doesn't start, or "npx: command not found". MCP clients don't always see your shell's PATH. Use the full path to npx as the command: which npx (macOS and Linux) or where npx (Windows) prints it.
  • "No KiCad project (.kicad_pro) in …". The folder given has no project within three levels. Give the project's folder or its .kicad_pro, or ask the assistant to open it.
  • Answers don't match what I see in KiCad. The server reads saved files. Save in KiCad, then ask again.
  • "The project changed on disk since these edits were proposed". Something was saved after the proposal. Ask for the edit again; the new proposal starts from the files as they are now.

Building a board

  • "KiCad's symbol libraries were not found on this computer." The local server reads KiCad's libraries from your KiCad install. Install KiCad, or set KICAD_SYMBOLS and KICAD_FOOTPRINTS to the folders that hold them. The hosted server needs neither.
  • The assistant doesn't offer to build a board (local server). Building needs version 0.2.0 or later of @crossprobe/mcp. npx -y @crossprobe/mcp --version shows yours; npx -y @crossprobe/mcp@latest fetches the newest.
  • "Nothing was built", with a list of problems. The spec names a symbol, pin or footprint the libraries don't have, or a symbol with pins its footprint has no pads for. The list says which; the assistant corrects the spec and builds again. This does not count as a build.
  • The report isn't clean. It lists what is left: unrouted connections, DRC results, parts that found no room. Ask the assistant to make the board larger or use four layers, or to say where a part belongs ("put J2 next to J1"). footprintWarnings are warnings inside a library footprint itself and don't count.
  • "That position is taken". A part was moved onto another. Ask the assistant to look at the picture and pick a free spot.
  • A part is far from where it belongs. Say so: "put the diode next to the fuse", "the connector at the left end of the bottom edge". See what you can say about the layout.

The hosted server

  • "Today's board build is used". An account without a plan gets one build a day; it counts again from 00:00 UTC. What was built can still be looked at and saved. See what it costs.
  • The assistant can't connect, or gets "401". The token is wrong, revoked, or was copied without its cp_ start. Make a new one under Connect an assistant… in the account menu.
  • "Too many requests without a valid access token" (429). Several attempts from your address had no valid token, and the address is turned away for a few minutes. Fix the token and try again later.
  • A build was stopped after 150 seconds. The board is too large or too dense for the time allowed. Fewer parts on the sheet, a larger board or four layers make it quicker.
  • I don't see what the assistant made. Ask it whether it saved: an unsaved proposal doesn't show in the app. Then open the project from the project menu (Open from your account), or with the link the assistant gave you.

Prefer a review without setup? Crossprobe's AI review runs in the browser on the same tools. Your first review is free. Review my KiCad project