← Registry

Design

perfboarddesigner.com

Manages perfboard and stripboard electronics projects by listing parts, creating and editing boards, placing components, wiring pins, and exporting project files.

1 endpoint12 known toolsFirst detected October 19, 2026Last detected October 19, 2026

ENDPOINT 1

https://mcp.perfboarddesigner.com/mcp

No auth detected

MCP server metadata

Name
perfboard-designer
Version
0.1.0
Capabilities
tools.listChangedresources.listChanged
Server instructions

Perfboard Designer (https://perfboarddesigner.com) is a browser editor for perfboard and stripboard layouts. You design a board here as a project file and give the user a link that opens it in the editor. The goal is a board that's right, looks neat and is easy to solder. 1. list_parts with no query: every part. Then get_part with ids: every part you use, in one call. 2. new_project (cols, rows, type) returns a projectId: pass it to every other tool. 3. edit_project: place parts (add_part) and route wires (add_wire with from/to, or a path with corners; ends can be pins by name, "U1.7", "D1.K"), all ops or none. Its reply gives where pins landed, the board's problems and, once there are no errors, its nets. Give expectNets (your netlist, e.g. [["U1.8", "R1.1"], ...]) once and every missing or extra connection is an error from then on. render_board draws the board as text to show free space, or with format "png" as a picture to look at. 4. Fix every error; warnings are likely mistakes. 5. Make it neat and solderable: look at render_board format "png". Parts in tidy rows near what they connect to, connectors at edges; straight wires, few corners and crossings, none over a part. Rework it, then check again. 6. make_share_link: give the user the link (and with store: true, where offered, a short one too). show_board shows them the board in the chat, where the client shows MCP Apps. Rules: holes are [column, row] from the top-left hole, from 0, 2.54 mm apart. A hole holds one part's pin or lead at most (two parts in one hole is an error) plus any number of wire ends, and everything in it is joined: to connect two parts, run a wire between their pins. A wire joins only the holes at its ends and corners, never a hole it passes over; wires may cross (no short, but avoid it). On a stripboard each strip joins its holes up to a cut (add_cuts). The full guide, with more on all this and on changing a board the user shares (read_share_link): the resource perfboard://docs/guide.

Known tools 12

list_parts

Lists the parts a project can place.

Inferred read-only
get_part

Everything needed to place parts: for each, which project file list it goes in, its pins (offsets from pin 1 at rotation 0) and pin labels, polarity, value unit, holes its body covers, and an example entry.

Inferred read-only
new_project

Starts a project kept here under a projectId: a blank board, or one of the example projects (perfboard://examples/.

Inferred read-only
edit_project

Changes a project kept here, by a list of ops applied in order: add_part, update_part (move, turn, change value or ref), remove_parts, add_wire (from/to, or a `path` of holes made into one wire per leg), update_wire, remove_wires, set_board, add_cuts / remove_cuts (stripboard), set_pad.

Inferred read-only
get_project

The whole project file of a project kept here, as the editor would save it (version 3), one entry per line.

Inferred read-only
validate_project

Checks a project file and lists every problem with where it is: entries the editor would leave out, unknown parts, pins off the board, two parts' pins or leads in one hole, overlapping parts, wires that connect nothing (a loose end, or no pins on their net), duplicate wires, a two-lead part with both leads on one net (shorted out), a wire passing over a pin or lead without ending there (so not joined to it), IC pins and two-lead parts' leads connected to nothing, supply rails shorted together, and on a stripboard, pins shorted by a strip or sitting in a cut hole.

Inferred read-only
get_nets

Which pins the board connects: every net with its name (from its pins, e.

Inferred read-only
get_pin_positions

Where every placed part's pins land, as [column, row] holes, with pin numbers and labels (e.

Inferred read-only
render_board

Draws the board as text, one cell per hole with column and row numbers: each part's pins by a key letter and pin number (a1, a2.

Inferred read-only
make_share_link

Turns a project into a link that opens it in Perfboard Designer: the project travels inside the link, so it works without any server.

Inferred read-only
read_share_link

Reads the project out of a Perfboard Designer share link (any of its forms: z=, json= or src=, which is downloaded; a stored project's short link too), so you can look at or change a board the user shared.

Inferred read-only
show_board

Shows the user a picture of the board right in the conversation, as the editor draws it, with a button that opens it in Perfboard Designer.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.perfboard-designer]
url = "https://mcp.perfboarddesigner.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "perfboard-designer": {
      "type": "http",
      "url": "https://mcp.perfboarddesigner.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: perfboard-designer
Remote MCP URL: https://mcp.perfboarddesigner.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "perfboard-designer": {
      "url": "https://mcp.perfboarddesigner.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "perfboard-designer": {
      "type": "http",
      "url": "https://mcp.perfboarddesigner.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "perfboard-designer",
  "transport": "streamable-http",
  "url": "https://mcp.perfboarddesigner.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.