3v3.dev Sign in

For agents · a hosted MCP

The PCB tool your agent can finish a board with.

Give Claude Code, Cursor, ChatGPT or any MCP client the same tools the editor uses. It places, routes, checks and exports Gerbers; you watch the board in your browser and take over any time.

Set up

One line, then ask for a board.

  1. Make a key on the Connect page. It is shown once.
  2. Add 3V3 to your agent (the line on the right).
  3. Ask for a board in plain words. Open app.3v3.dev to watch it happen.
# one line, then ask for a board
$ claude mcp add --transport http 3v3 https://mcp.3v3.dev/mcp \
    --header "Authorization: Bearer $V3_KEY"

> Make a 50 × 50 mm board with an ESP32-C3, USB-C power
  and a status LED. Route it and stop when the check is clean.

Five real runs

About four minutes, measured.

Five boards, each from one plain prompt to exported Gerbers by a real agent (Claude Code, Opus) on our hosted MCP. Uncut, every design-rule check clean.

BoardTimeTool callsDRC errorsModel cost
Relay module, 62 × 40 mm3:43790$1.36
555 blinker3:50770$1.45
Pico + I2S amplifier, 90 × 70 mm3:52340$1.42
USB-C to 3.3 V, 30 × 37 mm5:231010$1.94
ESP32-C3 + USB-C, 36 × 37 mm7:46500$2.61

Median 3 min 52 s. The transcripts, every tool call in them, are linked here at launch.

What it got wrong, too. In a trial run before these five, the agent made a coin-cell board 35 × 23 mm instead of the 30 × 20 asked for, because the battery holder alone is 33.5 mm, and it said so. On the USB-C board the status stayed amber for the pins a power-only design leaves empty on purpose; that one was ours to fix, and is fixed: a pin can now be marked “not connected” (6 October).

Your key, your boards.

  • Keys are shown once, stored only as a hash, rate-limited and revocable in one click.
  • A key can build and change your boards; it cannot touch your account, billing or other keys.
  • Every tool call your agent makes is logged on your account.
  • Your agent works only on your boards. Nobody else's are reachable.
More on trust