com.perfboarddesigner由 perfboarddesigner.com 发布官方发布者v0.1.0更新于 Nov 1, 2026
Design perfboard and stripboard layouts, check the wiring and get a link to open them in the editor.
设计洞洞板与条板电路布局：查询元件、放置元件、布线、检查连线，并生成可在 Perfboard Designer 编辑器中打开的分享链接。
Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/com.perfboarddesigner%2Fmcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"perfboard-designer": {
"type": "http",
"url": "https://mcp.perfboarddesigner.com/mcp"
}
}
}An MCP server that lets an AI agent (Claude, or any MCP client) design perfboard and stripboard layouts for Perfboard Designer. The agent looks up parts, writes the board as a project file, checks it, and gives you a share link. Clicking the link opens the board in the editor, where you can look at it and change it.
"Lay out a 555 LED blinker on a small perfboard and send me the link."
It runs on your computer (stdio), needs no account and saves nothing to disk; or it can be hosted
on Cloudflare Workers (below). While it runs it keeps the projects an agent is working on in memory, each under a projectId, so the agent sends
a project at most once and then changes it with small edits. The project file stays the source of
truth: get_project returns it, and every tool also takes a whole file instead of an id.
Node.js 22 or newer. It's on npm as
perfboard-designer-mcp, which npx
downloads the first time.
Claude Code:
Claude Desktop (claude_desktop_config.json, Settings → Developer → Edit Config) and other
clients that take a command:
To run it from this repo instead, build it and use node /path/to/perfboard-designer/mcp/dist/server.js
as the command:
Links open the public editor, https://perfboarddesigner.com/app/. To point them at another copy (a
local dev server, say), set PERFBOARD_EDITOR_URL in the server's environment:
The server works on its own, without the hosted Worker. It
only points at it for two extras, each set in the server's environment like PERFBOARD_EDITOR_URL,
public unless set, and off to do without (agents are then not offered it):
Point them at a local Worker with http://localhost:8787/render.svg and http://localhost:8787.
Every tool that reads a project takes either projectId or the whole file as project. Kept
projects last as long as the server process (the 200 most recently used); on Cloudflare, 30 days
after they were last used.
Its instructions to agents are kept short (clients cut them off at about 2 KB); the full guide is
the resource perfboard://docs/guide (src/guide.ts).
It also serves the format as resources: perfboard://docs/project-file (the project file
format, field by field), perfboard://docs/share-links (the link format), perfboard://parts
(the whole parts catalog as JSON), and example projects: perfboard://examples/555-led-blinker (a
555 LED blinker on a perfboard, all wired with jumpers) and
perfboard://examples/555-led-blinker-stripboard (the same circuit on a stripboard), read from
../examples/.
The public copy runs at https://mcp.perfboarddesigner.com/mcp; how to add it to Claude Code,
claude.ai, ChatGPT, Cursor and other clients is on https://perfboarddesigner.com/mcp-server/
(../mcp-server/index.html).
The same server also runs as a Cloudflare Worker,
so an MCP client can reach it over the web with nothing installed: Streamable HTTP at /mcp
(src/worker.ts). It's stateless, every request getting a fresh server, so kept projects can't
live in memory: each is kept in its own Durable Object (ProjectHolder), named by its
projectId, and forgotten after 30 days unused. Project ids are random, so they can't be guessed.
There's no sign-in: anyone with the address can use it.
It also draws boards: /render.svg? followed by a share link's part after the # (name=…&z=…
or json=…; src= links aren't fetched) answers with an SVG picture of that board, drawn by the
editor's own board renderer (../src/board-render/) with the part icons baked in. /render.png?
with the same parameters answers with a PNG of it instead, for places that don't show SVG, such as
chat apps and link previews. An address says everything in its picture, so it's cached for good
(src/image-requests.ts).
The PNGs, from /render.png and render_board, are drawn from the same SVG by
resvg, compiled to WebAssembly (@resvg/resvg-wasm,
MPL-2.0), so they come out the same from the Worker and from stdio (src/board-png.ts).
Drawing one takes around a tenth of a second of CPU for a small board, far more than the Workers
Free plan's 10 ms a request, so the hosted server needs a paid plan to draw them.
So pictures aren't drawn again for every request, each Cloudflare data center keeps a copy of
every picture and stored project file it serves (the Workers Cache
API), for as long as its
Cache-Control says: a year for /render.*, a day for stored projects. Repeat requests there
are answered from it (CF-Cache-Status: HIT) without drawing again or waking the stored project's
Durable Object (edgeCached() in src/worker.ts). Only answers that
worked are kept, so an unknown id is looked up again next time. After a change to how boards are
drawn, old pictures stay until they expire or the zone's cache is purged in the Cloudflare
dashboard. The cache does nothing on the workers.dev address, only on the custom domains.
A share link carries the whole project, so it works without any server, but it gets long. The
Worker can also store a project under a short id and serve it, at
https://projects.perfboarddesigner.com (the same Worker, at its own address so the storage could
move to a Worker of its own without breaking links). It's the project storage behind short links,
for agents (make_share_link with store) and for people (the editor's Share dialog), documented
for both in docs/share-links.md:
"Mágneses kapcsoló!" → magneses-kapcsolo), at most 40 characters, ignoring case. If another
board has that id, a few characters of the board's SHA-256 are added (led-blinker-08196a);
storing the same board again under the same id gives the same id back. With neither, the id is
the hash. Ids shorter than 3 characters or naming the server's own addresses (mcp, render,
projects…) always get the hash added.p= share link (…/app/#name=LED%20blinker&p=led-blinker), which the
editor opens from this storage without asking. Stored anywhere else (PERFBOARD_PROJECTS_URL),
it's a src= link to the file instead, which any editor opens. Anyone with a link can read the
board.StoredProjectHolder) named by its id, so two boards
stored at once can't both get an id (src/stored-projects.ts, src/project-requests.ts). The
stdio server stores through POST /projects.There's no sign-in or rate limit yet: anyone can store projects.
The listing is public and requires no token. Deploy from mcp/:
Then query it:
Omit q to list all indexed projects. Search matches a literal substring of the id or name
(ASCII case-insensitive). limit defaults to 20 and accepts 1–100. The response is
{projects: [{id, name?, storedAt, link, file, image, png}], nextCursor}; storedAt is the
original save time in Unix milliseconds. Pass nextCursor as the URL-encoded cursor query
parameter with the same q to get the next page; null means there are no more results.
Listings are not cached and do not extend projects' lifetimes.
The StoredProjectIndex Durable Object tracks new saves and removes expired projects. Existing
projects from before this index was deployed appear when saved again or read from their storage
object (an edge-cache hit does not reach storage). This is not a complete historical inventory:
there was no central index before. Temporary MCP working projects are not included.
For local use, run npm run worker:dev and query http://localhost:8787/projects.
Try it locally (at http://localhost:8787/mcp):
Publish it to your Cloudflare account (npx wrangler login once first):
Both build first; worker:dev serves stored projects at http://localhost:8787 too. wrangler.toml
is the Worker's config: its name, its domains, the Durable Object bindings and, in [vars],
PERFBOARD_EDITOR_URL for where links open and PERFBOARD_PROJECTS_URL for where stored projects
are served. Then add it to a client by its
address:
On the Workers Free plan a request gets 10 ms of CPU time, which checking a big board can run over; the Paid plan allows far more.
The package is on npm as perfboard-designer-mcp, and the server is listed in the
MCP Registry as com.perfboarddesigner/mcp, described
by server.json: the hosted address (remotes) and the npm package (packages). The registry
checks that package.json's mcpName is that name, and that you own perfboarddesigner.com, by a
DNS TXT record on the apex domain holding a public key.
npm version patch (or minor), and set the same version in server.json,
both at the top and in its npm package entry.npm publish (it builds first; npm asks for 2FA). Wait until npm view perfboard-designer-mcp version shows the new version.npm run worker:deploy.mcp-publisher:
mcp-publisher validate, then mcp-publisher login dns --domain perfboarddesigner.com --private-key "$PRIVATE_KEY" and mcp-publisher publish, run in mcp/.The key pair is made once with OpenSSL 3, its public half added as a TXT record on
perfboarddesigner.com (Cloudflare DNS); keep key.pem outside the repo:
Wires are insulated jumpers: a wire joins only the holes at its two ends. Running over a hole
doesn't connect it, and two wires crossing aren't shorted, so a crossing is fine (the editor marks
it so it doesn't pass for a joint, and the 3D view arches the upper wire). A hole takes one part's
pin or lead at most (a second part there is an error, as on a real board) plus any number of wire
ends, and everything in a hole is joined: to connect two parts, run a wire between their pins.
A jumper can lie on the solder side (side: "bottom", format version 9): it joins its end holes the same way but never crosses a top wire.
On a stripboard, every hole along a strip is joined up to the next cut, and a cut hole connects to
nothing. get_nets and validate_project work this out with the same code as the
editor's Nets panel, so they agree with what you see there.
src/ is the server: create-server.ts puts it together, server.ts runs it over stdio and
worker.ts on Cloudflare, tools/ holds the tools by group, resources.ts
the documents it serves, project-handles.ts the kept projects (and where they're stored), edit-ops.ts and
edit-project.ts edit_project's ops, validate.ts the checks, guide.ts its instructions and
guide, board-view/ the page show_board shows the board in (an MCP App; view.ts runs in the
client's frame and speaks the few MCP Apps messages it needs itself, so the page stays a few KB). It builds on the editor's own pure code, all of it taken through editor.ts, the one file
that imports from ../src/: the project file reader, share-link code, pin positions, nets
(nets.ts) and wire crossings (wire-crossings.ts) in ../src/project-file/, the part
definitions and part geometry in ../src/parts/, and the board renderer (../src/board-render/)
for pictures of a board. That way it always agrees with the editor about the format, the parts and what's
connected. The editor never imports anything from here. npm run build bundles that code and the MCP SDK into
a single dist/server.js (and dist/worker.js for Cloudflare) with no runtime dependencies,
and bakes in the docs and examples it serves, the part icons its pictures embed and
show_board's page (board-view/view.html with view.ts bundled for the browser into it). PNG pictures
also need resvg's WebAssembly, which the build copies beside them as dist/resvg.wasm (uploaded
with the Worker), and fonts, since resvg can't use the system's: Noto Sans and Noto Sans Mono,
cut down to the characters boards use, in fonts/ (SIL Open Font License; fonts/README.md
says how to remake them).
The shared reader supports format 8, including optional independent requirements; format 7
adds project-scoped component instanceId fields. edit_project preserves all intended nets,
gives new parts fresh identities, and includes them in the requirement inventory without
assigning connections. Removed required parts remain reportable by identity, even if another
part reuses their reference name. A schematic field from older editors is ignored.
When requirements.validate is true, checks also compare the board with the saved requirements:
missing components/pins, missing connections and unexpected joins are errors; incomplete coverage
is a warning and never described as a full requirement match. Unspecified pins remain unchecked.
This is independent of the existing complete-list expectNets contract, which is unchanged.
The project-format resource includes the requirement types.
Deploy this shared reader with the frontend before sharing version-8 files through hosted storage. Embedded links remain usable without hosted storage.
来源：mcp/README.md，提交 2e9d5f9
List parts
Lists the parts a project can place. Without a query: every part, grouped by category, as its id with its name and pin count; call it this way once to see what there is. With a query: the parts whose id, name, category or keywords contain all its words, or the closest ones when none do. Each part's `id` is its definitionId in the project file; use get_part for its pins and how to place it.
kindqueryGet parts
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. Ask for every part you use in one call with `ids`.
ididsNew project
Starts a project kept here under a projectId: a blank board, or one of the example projects (perfboard://examples/...) to copy from. Returns the projectId and the project file. Then add parts and wires with edit_project, and pass the projectId to every other tool instead of the whole file.
colsnamerowstypestripsexampleEdit 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 (a note on a hole). If any op can't be done, none are. Returns what changed, where the pins of added or moved parts landed, and the board checked as validate_project does (with any expectNets remembered for it); when it has no errors, also its nets. get_project returns the whole file. The goal is a board that's right, looks neat and is easy to solder, not just the shortest wires: parts in tidy rows near what they connect to, connectors at the edges, straight wires with few corners and no crossing you can avoid, none over a part's body. Before giving the user the link, look at it (render_board with format "png"), rework what's messy and check it again.
ops必填projectprojectIdexpectNetsGet project
The whole project file of a project kept here, as the editor would save it (through version 8, preserving component identities and optional requirements), one entry per line.
projectId必填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. With expectNets, every connection missing from the board or extra on it is an error. Enabled saved requirements also check intended connections, missing components/pins and unused pins; unspecified pins produce an incomplete-coverage warning, not a full match. Wires crossing each other are fine (insulated jumpers) and only listed in notes. Fix all errors before making a link. A project sent whole is kept here: the reply's projectId stands for it in every other tool.
projectprojectIdexpectNetsGet nets
Which pins the board connects: every net with its name (from its pins, e.g. GND), its pins ("U1.8 VCC" for a chip's pin, "D1.K" or "C1.+" for a polarized lead, "R1.1" otherwise) and the wires on it (indexes into wires). Also pins connected to nothing, wires that connect no pins, junctions (holes where three or more things are joined) and crossings (where a wire goes over another wire or over a hole without joining it). Wires are insulated jumpers: a wire joins only the holes at its two ends, so crossings are information, not connections or shorts. On a stripboard the strips connect too.
projectprojectIdGet pin positions
Where every placed part's pins land, as [column, row] holes, with pin numbers and labels (e.g. U1 pin 8 VCC), after rotation, plus holes a part's body covers. Use it to route wires to the right holes. The project file doesn't store these: they follow from each part's anchor, rotation and footprint.
refsprojectprojectIdRender 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...), holes under a part's body, wire ends, the holes a wire runs over without joining them, strip cuts and holes with notes. Below it, which part each key is and every wire with its ends and net. Use it to see where there's free space and how wires run before placing parts or routing more. With format "png", a picture of the board as the editor draws it instead, to see how it looks: parts' bodies and where they reach, labels, wire colours. To show the user the board, use show_board.
areaformatprojectprojectIdMake 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. Give the link to the user. Also returns `image`, the address of an SVG picture of the board (as the editor draws it), for showing it where images from links display, e.g. in Markdown (not in Claude or ChatGPT, which don't load them: show_board shows the board there). With store, the project is also stored on the Perfboard Designer server under a short id, and `stored` gives a short link to it, its file and its pictures (SVG and PNG): give the user both links. The project is validated first (against enabled saved requirements and expectNets too, given or remembered for its projectId); a project with errors gets the list of problems instead of a link, unless allowErrors is set.
namestoreprojectstoreAseditorUrlprojectIdexpectNetsallowErrorsRead share link
Reads the project out of a Perfboard Designer share link (z=, json=, downloaded src=, or a stored short link). Returns a project file through version 8, preserving component identities and optional requirements, kept under the returned projectId: change it with edit_project.
link必填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. Only in clients that show MCP Apps (e.g. Claude, ChatGPT); elsewhere the user sees nothing, so give them make_share_link's link too. The picture goes to the user, not to you: to look at the board yourself, use render_board.
nameprojectprojectId已满足适用检查项的 90%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
请在仓库或注册中心条目中声明许可证。
claude mcp add --scope user perfboard -- npx -y perfboard-designer-mcp{ "mcpServers": { "perfboard": { "command": "npx", "args": ["-y", "perfboard-designer-mcp"] } }}cd mcpnpm installnpm run build{ "mcpServers": { "perfboard": { "command": "npx", "args": ["-y", "perfboard-designer-mcp"], "env": {"PERFBOARD_EDITOR_URL": "http://localhost:3000/app/"} } }}npm run worker:deploycurl 'https://projects.perfboarddesigner.com/projects?q=blinker&limit=20'npm run worker:devnpm run worker:deployclaude mcp add --transport http perfboard https://perfboard-designer-mcp.<your-subdomain>.workers.dev/mcpopenssl genpkey -algorithm Ed25519 -out ~/.config/mcp-registry/key.pemecho "v=MCPv1; k=ed25519; p=$(openssl pkey -in ~/.config/mcp-registry/key.pem -pubout -outform DER | tail -c 32 | base64)"PRIVATE_KEY="$(openssl pkey -in ~/.config/mcp-registry/key.pem -noout -text | grep -A3 'priv:' | tail -n +2 | tr -d ' :\n')"