MCP server — your own agent, on your board
Claude, Codex or Cursor can place, route, pour, check and solve power on the board open in WireFrame.
WireFrame speaks the Model Context Protocol, so the agent you already work in can work on a real board: it gets 33 tools, and through one of them the 117 design tools WireFrame's own Copilot uses — the placer and the layout optimiser, the router's stages, copper pours, the power and signal-integrity solvers, the board check. Every answer comes from the application you have open, on the project you have open.
What it does
33 tools, 117 behind them
Your agent opens or starts the project and writes the BOM, the wiring and the sheets itself; call_tool reaches every design tool by name; ask_penalty and run_command hand a job to WireFrame's agent. Listing the tools costs nothing.
Measured, not described
score_board over MCP returns the number the panel would show — the same engines, the same board, a different caller.
Nothing changes until it is applied
Layouts, patches and power fixes are worked out on a copy; one apply step puts them on the board, one undo takes them off.
Some things wait for you
A high-speed patch or a power fix is applied only after you approve it in WireFrame's own window.
On your machine
A small bridge and a local socket in your user folder — no network port, and no copy of the project anywhere else.
You pay for changes
A call counts when it changes the design or puts WireFrame's agent to work. Reading, checking, a layout tried and not applied, connecting and every refusal are free.
Your agent's reasoning, WireFrame's engines
Ask in plain words and the agent picks the tool: "find where the 3V3 rail loses its voltage" sets the rail up and runs the DC IR drop solve; "try four placements and keep the one that routes best" lays the board out four ways on copies and compares them; "is the USB pair at 90 Ω?" asks the impedance solver on this stack-up. The thinking is your agent's. The numbers are WireFrame's, from the same code that answers the Copilot panel.
Or let WireFrame's agent do it
ask_penalty hands the Copilot one job and run_command a slash command such as /layout place,route. WireFrame's agent knows which stage has to run before which, and its turn spends your plan's AI credits exactly as it would if you had typed it in the panel. Most work mixes the two: WireFrame's agent lays the board out, yours reads the result and checks it.
What it will not do
It works on the active project — it can open another or start a new one, and closes one only when its work is saved — it does not export Gerbers — do that from the app — and only one agent may be connected to a WireFrame at a time. Pressing Allow puts it in command: it decides the parts, the wiring and the layout, and WireFrame's checks still refuse a part that fails them or an edit that introduces an error. A high-speed patch or a power fix still waits for your approval in WireFrame's own window.
The details
| Protocol | Model Context Protocol over stdio, version 2025-06-18 |
|---|---|
| Clients | Any stdio MCP client; the guide has the setup for Claude Desktop (config file or a .mcpb extension), Claude Code, Codex, Cursor and VS Code |
| Tools | 33 offered to the client; 117 design tools through call_tool with a schematic and board open |
| Plans | Pro: 500 tool calls a month · Max: no monthly ceiling · not in Free |
| Top-up | 7,999 tool calls for $59, valid 12 months, for Pro |
| Counted | a change to the design or a job for WireFrame's agent; reads are free from WireFrame 2.0.3 |
| Transport | a local socket in your user folder; no network port |
| Ships in | WireFrame 2.0.1 |
How to start
- Install WireFrame 2.0.3 or later and sign in on Pro or Max.
- Add WireFrame to your agent — Claude Desktop, Claude Code, Codex, Cursor or VS Code; the guide has the line for each.
- Ask your agent: it opens the project, or starts a new one, and works on the one that is active.
Questions
Which agents does it work with?
Any MCP client that runs a local stdio server: Claude Desktop, Claude Code, Codex, Cursor and VS Code among them. The guide has the exact line for each.
How do I set it up with Claude Desktop?
Five steps, in this order: install the extension from the download page, open WireFrame, turn the extension on in Claude's Settings, create or open your project, then press Allow in WireFrame's AI panel.
Does it need WireFrame open?
Yes. The tools work on the board in front of you, so WireFrame has to be running with the project open. Without it the agent still connects, offers no tools, and says why.
How are calls counted?
From WireFrame 2.0.3 a call counts when it changes the design — the BOM, the wiring, the sheets, a layout applied — or puts WireFrame's own agent to work. Reading the design and the guides, the checks, the analyses and a layout tried and not applied are free, and so are connecting, listing the tools and a refused call. ask_penalty, run_command and build_blocks also spend the AI credits of WireFrame's own agent. WireFrame 2.0.1 and 2.0.2 count every call, a read included.
Do I need a paid plan?
Yes — Pro includes 500 tool calls a month and Max has no monthly ceiling. MCP is not in Free.