perfboard-designer-mcp 0.1.0 → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +46 -18
  2. package/dist/server.js +25 -10
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -15,35 +15,39 @@ truth: `get_project` returns it, and every tool also takes a whole file instead
15
15
 
16
16
  ## Setup
17
17
 
18
- Node.js 22 or newer. Build it from this repo:
19
-
20
- ```bash
21
- cd mcp
22
- npm install
23
- npm run build
24
- ```
25
-
26
- Then add it to your MCP client, using the absolute path to `dist/server.js`.
18
+ Node.js 22 or newer. It's on npm as
19
+ [`perfboard-designer-mcp`](https://www.npmjs.com/package/perfboard-designer-mcp), which `npx`
20
+ downloads the first time.
27
21
 
28
22
  **Claude Code:**
29
23
 
30
24
  ```bash
31
- claude mcp add perfboard -- node /path/to/perfboard-designer/mcp/dist/server.js
25
+ claude mcp add --scope user perfboard -- npx -y perfboard-designer-mcp
32
26
  ```
33
27
 
34
- **Claude Desktop** (`claude_desktop_config.json`) and other clients that take a command:
28
+ **Claude Desktop** (`claude_desktop_config.json`, Settings → Developer → Edit Config) and other
29
+ clients that take a command:
35
30
 
36
31
  ```json
37
32
  {
38
33
  "mcpServers": {
39
34
  "perfboard": {
40
- "command": "node",
41
- "args": ["/path/to/perfboard-designer/mcp/dist/server.js"]
35
+ "command": "npx",
36
+ "args": ["-y", "perfboard-designer-mcp"]
42
37
  }
43
38
  }
44
39
  }
45
40
  ```
46
41
 
42
+ To run it from this repo instead, build it and use `node /path/to/perfboard-designer/mcp/dist/server.js`
43
+ as the command:
44
+
45
+ ```bash
46
+ cd mcp
47
+ npm install
48
+ npm run build
49
+ ```
50
+
47
51
  Links open the public editor, https://perfboarddesigner.com/app/. To point them at another copy (a
48
52
  local dev server, say), set `PERFBOARD_EDITOR_URL` in the server's environment:
49
53
 
@@ -51,17 +55,14 @@ local dev server, say), set `PERFBOARD_EDITOR_URL` in the server's environment:
51
55
  {
52
56
  "mcpServers": {
53
57
  "perfboard": {
54
- "command": "node",
55
- "args": ["/path/to/perfboard-designer/mcp/dist/server.js"],
58
+ "command": "npx",
59
+ "args": ["-y", "perfboard-designer-mcp"],
56
60
  "env": {"PERFBOARD_EDITOR_URL": "http://localhost:3000/app/"}
57
61
  }
58
62
  }
59
63
  }
60
64
  ```
61
65
 
62
- Once the package is published to npm, `npx -y perfboard-designer-mcp` replaces
63
- `node /path/.../server.js` in both.
64
-
65
66
  The server works on its own, without the [hosted Worker](#hosting-it-on-cloudflare-workers). It
66
67
  only points at it for two extras, each set in the server's environment like `PERFBOARD_EDITOR_URL`,
67
68
  public unless set, and `off` to do without (agents are then not offered it):
@@ -199,6 +200,32 @@ claude mcp add --transport http perfboard https://perfboard-designer-mcp.<your-s
199
200
  On the Workers Free plan a request gets 10 ms of CPU time, which checking a big board can run
200
201
  over; the Paid plan allows far more.
201
202
 
203
+ ## Publishing a release
204
+
205
+ The package is on npm as `perfboard-designer-mcp`, and the server is listed in the
206
+ [MCP Registry](https://registry.modelcontextprotocol.io) as `com.perfboarddesigner/mcp`, described
207
+ by `server.json`: the hosted address (`remotes`) and the npm package (`packages`). The registry
208
+ checks that `package.json`'s `mcpName` is that name, and that you own `perfboarddesigner.com`, by a
209
+ DNS TXT record on the apex domain holding a public key.
210
+
211
+ 1. Bump the version: `npm version patch` (or `minor`), and set the same `version` in `server.json`,
212
+ both at the top and in its npm package entry.
213
+ 2. `npm publish` (it builds first; npm asks for 2FA). Wait until `npm view perfboard-designer-mcp
214
+ version` shows the new version.
215
+ 3. Deploy the Worker if the server changed: `npm run worker:deploy`.
216
+ 4. Publish to the registry with [`mcp-publisher`](https://github.com/modelcontextprotocol/registry/releases):
217
+ `mcp-publisher validate`, then `mcp-publisher login dns --domain perfboarddesigner.com
218
+ --private-key "$PRIVATE_KEY"` and `mcp-publisher publish`, run in `mcp/`.
219
+
220
+ The key pair is made once with OpenSSL 3, its public half added as a TXT record on
221
+ `perfboarddesigner.com` (Cloudflare DNS); keep `key.pem` outside the repo:
222
+
223
+ ```bash
224
+ openssl genpkey -algorithm Ed25519 -out ~/.config/mcp-registry/key.pem
225
+ echo "v=MCPv1; k=ed25519; p=$(openssl pkey -in ~/.config/mcp-registry/key.pem -pubout -outform DER | tail -c 32 | base64)"
226
+ PRIVATE_KEY="$(openssl pkey -in ~/.config/mcp-registry/key.pem -noout -text | grep -A3 'priv:' | tail -n +2 | tr -d ' :\n')"
227
+ ```
228
+
202
229
  ## How things connect
203
230
 
204
231
  Wires are insulated jumpers: a wire joins only the holes at its two ends. Running over a hole
@@ -237,4 +264,5 @@ says how to remake them).
237
264
  | `npm run typecheck` | Type-check the server and the editor code it imports |
238
265
  | `npm run worker:dev` | Run the Cloudflare Worker locally, at http://localhost:8787/mcp |
239
266
  | `npm run worker:deploy` | Publish the Worker to Cloudflare |
267
+ | `npm version patch`, then `npm publish` | Release a new version to npm (`prepublishOnly` builds first; npm asks for 2FA) |
240
268
  | `npm run inspect` | Open the server in the [MCP Inspector](https://github.com/modelcontextprotocol/inspector) to try the tools by hand |
package/dist/server.js CHANGED
@@ -38115,20 +38115,21 @@ var EMPTY_COMPLETION_RESULT = {
38115
38115
  init_define_COMPONENT_ICONS();
38116
38116
  init_define_EXAMPLE_PROJECTS();
38117
38117
  init_define_PNG_FONTS();
38118
- var 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.
38118
+ var 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.
38119
38119
 
38120
38120
  1. list_parts with no query: every part. Then get_part with ids: every part you use, in one call.
38121
38121
  2. new_project (cols, rows, type) returns a projectId: pass it to every other tool.
38122
38122
  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.
38123
38123
  4. Fix every error; warnings are likely mistakes.
38124
- 5. 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.
38124
+ 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.
38125
+ 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.
38125
38126
 
38126
- 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. On a stripboard each strip joins its holes up to a cut (add_cuts).
38127
+ 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).
38127
38128
 
38128
38129
  The full guide, with more on all this and on changing a board the user shares (read_share_link): the resource perfboard://docs/guide.`;
38129
38130
  var GUIDE = `# Designing a board with Perfboard Designer
38130
38131
 
38131
- Perfboard Designer (https://perfboarddesigner.com) is a browser editor for perfboard and stripboard layouts. With these tools you design a board as a project file (JSON, format version 3) and give the user a link that opens it in the editor, where they can see and change it.
38132
+ Perfboard Designer (https://perfboarddesigner.com) is a browser editor for perfboard and stripboard layouts. With these tools you design a board as a project file (JSON, format version 3) and give the user a link that opens it in the editor, where they can see and change it. The goal is a board that's electrically right, looks neat and is easy to solder by hand: the user will build it.
38132
38133
 
38133
38134
  ## Workflow
38134
38135
 
@@ -38137,8 +38138,9 @@ Perfboard Designer (https://perfboarddesigner.com) is a browser editor for perfb
38137
38138
  3. edit_project with a list of ops: place parts (add_part with the part's id and "at", or "from" and "to" for a two-lead part) and route wires (add_wire with "from" and "to", or a "path" of holes for a wire with corners; any of these can be a pin by name, "U1.7" or "D1.K", for the hole it's in). If any op can't be done, none are. Each reply says where the new parts' pins landed and checks the board; once it has no errors, the reply lists its nets too.
38138
38139
  4. Check the circuit is the one you meant: the nets in edit_project's reply (pins named like "U1.8 VCC", "D1.K", "R1.1"), or get_nets for junctions and crossings too. Give expectNets (your netlist, e.g. [["U1.8", "U1.4", "R1.1", "J1.1"], ...]) once, to edit_project or validate_project, and every missing or extra connection is reported as an error from then on. render_board draws the board as text, one cell per hole: use it to see free space and where wires run before you place or route more. With format "png" it draws a picture of the board instead, as the editor shows it: look at it to see how the board comes out, e.g. a part's body reaching off the board, labels and wire colours. A big board's picture is scaled down; give area to zoom in.
38139
38140
  5. Fix every error. Warnings are likely mistakes, such as two pins of one part shorted by a strip or a resistor's two leads joined by wires, a wire passing over a pin without joining it, a lead or wires connected to nothing, or two supply rails shorted. validate_project lists notes too.
38140
- 6. make_share_link with the projectId: give the user the link it returns. The link carries the whole board and needs no server; a server may also offer these extras. It returns "image", the address of an SVG picture of the board as the editor draws it: show it where images from links display, e.g. Markdown ![board](image) (Claude and ChatGPT don't load those). With store: true (or storeAs: "led-blinker", the id you'd like), the project is also stored on the Perfboard Designer server, and "stored" gives its id, a short link, its file and its pictures (png too, for places that don't show SVG). Give the user both links: the short one needs the server, the long one works without it. A stored project never changes: store again after changing the board, for a new id.
38141
- 7. show_board shows the user the board right in the chat, as the editor draws it, with a button that opens it in the editor: in clients that show MCP Apps (e.g. Claude, ChatGPT), where a Markdown image from a link isn't shown. Elsewhere it shows nothing, so give the link too. The picture goes to the user, not to you: render_board with format "png" is the one for you to look at.
38141
+ 6. Make it neat and solderable (see Laying it out well): look at render_board with format "png", then move parts and reroute wires until it's tidy, and check again (errors, warnings, expectNets). Don't stop at the first board that's right.
38142
+ 7. make_share_link with the projectId: give the user the link it returns. The link carries the whole board and needs no server; a server may also offer these extras. It returns "image", the address of an SVG picture of the board as the editor draws it: show it where images from links display, e.g. Markdown ![board](image) (Claude and ChatGPT don't load those). With store: true (or storeAs: "led-blinker", the id you'd like), the project is also stored on the Perfboard Designer server, and "stored" gives its id, a short link, its file and its pictures (png too, for places that don't show SVG). Give the user both links: the short one needs the server, the long one works without it. A stored project never changes: store again after changing the board, for a new id.
38143
+ 8. show_board shows the user the board right in the chat, as the editor draws it, with a button that opens it in the editor: in clients that show MCP Apps (e.g. Claude, ChatGPT), where a Markdown image from a link isn't shown. Elsewhere it shows nothing, so give the link too. The picture goes to the user, not to you: render_board with format "png" is the one for you to look at.
38142
38144
 
38143
38145
  ## The board
38144
38146
 
@@ -38150,7 +38152,20 @@ A hole holds at most one part's pin or lead: a second part's pin or lead in the
38150
38152
 
38151
38153
  ## How things connect
38152
38154
 
38153
- Wires are insulated jumpers: a wire joins only the holes at its two ends (and a path's corners), never a hole it passes over, and wires may cross each other (that's fine, not a short). On a stripboard, every hole along a strip is already connected up to the next cut, and a cut hole connects to nothing: cut strips (add_cuts) to separate them, e.g. under a chip so its two pin rows aren't shorted.
38155
+ Wires are insulated jumpers: a wire joins only the holes at its two ends (and a path's corners), never a hole it passes over, and wires may cross each other (that's not a short, but avoid it: see Laying it out well). On a stripboard, every hole along a strip is already connected up to the next cut, and a cut hole connects to nothing: cut strips (add_cuts) to separate them, e.g. under a chip so its two pin rows aren't shorted.
38156
+
38157
+ ## Laying it out well
38158
+
38159
+ A board that's right isn't done until it looks neat and someone can easily solder it. Prefer a readable, compact, physically practical layout, like one a person would lay out by hand, over the shortest total wire length:
38160
+
38161
+ - Place parts first, wires after. Put the main chip or module near the middle and each part close to the pins it connects to, so most wires are short. Keep parts that belong together (a timing resistor and capacitor, a decoupling capacitor and its chip's supply pins) next to each other.
38162
+ - Line parts up: two-lead parts straight (horizontal or vertical) and in tidy rows, polarized parts the same way round where you can, and a gap of a hole or two between parts for wires and fingers. Leave the board no bigger than it needs to be, with a hole or so of margin at the edges.
38163
+ - Follow the signal: inputs and connectors at one edge, outputs at the other, and supply rails (VCC, GND) along the edges or in a row each, so they're easy to follow and to reach.
38164
+ - Leave room to solder: every lead straight and fully on the board, and a part's body not covering holes that wires or other parts need.
38165
+ - Route wires straight, horizontal or vertical, with as few corners as possible; never diagonal unless it's a very short hop. Avoid crossings: they're allowed (wires are insulated), but every one makes the board harder to follow and to build. Moving a part or swapping which way it's placed often removes one.
38166
+ - Don't run wires over parts' bodies or across chips: go around them. Don't run a wire across a hole holding a pin it doesn't connect to (validate_project warns about that).
38167
+ - On a stripboard, let the strips do the connecting: place parts so pins that share a net sit on one strip, and use wires and cuts only where strips can't.
38168
+ - Look at the board as you go: render_board shows free space as text; with format "png" you see it as the user will. Tidy it up before you give the user the link: fewer crossings, fewer corners, straighter rows. Never break a connection to make it look better.
38154
38169
 
38155
38170
  ## More
38156
38171
 
@@ -42655,7 +42670,7 @@ function registerProjectTools(server) {
42655
42670
  });
42656
42671
  server.registerTool("edit_project", {
42657
42672
  title: "Edit project",
42658
- description: "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. 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.",
42673
+ description: "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. 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.",
42659
42674
  inputSchema: {
42660
42675
  projectId: projectIdInput,
42661
42676
  project: projectInput.describe("A whole project file to start from instead of a projectId: it's kept here and the reply gives its new projectId."),
@@ -43865,7 +43880,7 @@ function registerShowBoardTool(server, DEFAULT_EDITOR_URL) {
43865
43880
  description: "The page show_board shows the board in.",
43866
43881
  // The picture is a data: image, and the page loads nothing else.
43867
43882
  _meta: { ui: { prefersBorder: false } }
43868
- }, async (uri) => ({ contents: [{ uri: uri.href, mimeType: p, text: '<!doctype html>\n<html lang="en">\n<head>\n<meta charset="utf-8">\n<meta name="viewport" content="width=device-width, initial-scale=1">\n<title>Perfboard board</title>\n<style>\n :root { color-scheme: light dark; font-family: system-ui, sans-serif; font-size: 14px; }\n body { margin: 0; background: transparent; color: CanvasText; }\n figure { margin: 0; display: flex; flex-direction: column; gap: 8px; }\n img { display: block; width: 100%; height: auto; border-radius: 6px; }\n img:not([src]) { display: none; }\n figcaption { display: flex; align-items: center; justify-content: space-between; gap: 12px; flex-wrap: wrap; }\n #caption { opacity: 0.75; }\n button { font: inherit; padding: 6px 12px; border-radius: 6px; border: 1px solid #1f7a3a; background: #1f7a3a; color: #fff; cursor: pointer; }\n button:hover { background: #18602e; }\n button[hidden] { display: none; }\n</style>\n</head>\n<body>\n<figure>\n <img id="board" alt="">\n <figcaption>\n <span id="caption">Drawing the board\u2026</span>\n <button id="open" type="button" hidden>Open in Perfboard Designer</button>\n </figcaption>\n</figure>\n<script type="module">var f="2026-01-26",r=document.getElementById("board"),a=document.getElementById("caption"),u=document.getElementById("open"),i,g=1,s=new Map,o=t=>window.parent.postMessage({jsonrpc:"2.0",...t},"*");function m(t,e){let n=g++;return o({id:n,method:t,params:e}),new Promise(p=>s.set(n,p))}function h(t){let e=t._meta?.board;if(t.isError||!e){a.textContent=t.content?.find(n=>n.type==="text")?.text??"The board couldn\'t be shown.";return}r.src=`data:image/svg+xml;charset=utf-8,${encodeURIComponent(e.svg)}`,r.alt=e.caption,a.textContent=e.caption,i=e.link,u.hidden=!i}window.addEventListener("message",({source:t,data:e})=>{t!==window.parent||e?.jsonrpc!=="2.0"||(e.method===void 0?(s.get(e.id)?.(e.result),s.delete(e.id)):e.method==="ui/notifications/tool-result"?h(e.params??{}):e.id!==void 0&&o({id:e.id,result:{}}))});u.addEventListener("click",()=>{i&&m("ui/open-link",{url:i})});var c=0,l=0;function d(){let t=document.documentElement,e=Math.ceil(t.getBoundingClientRect().height),n=Math.ceil(window.innerWidth);n===c&&e===l||(c=n,l=e,o({method:"ui/notifications/size-changed",params:{width:n,height:e}}))}await m("ui/initialize",{protocolVersion:f,appInfo:{name:"Perfboard Designer board",version:"0.1.0"},appCapabilities:{}});o({method:"ui/notifications/initialized",params:{}});new ResizeObserver(()=>requestAnimationFrame(d)).observe(document.body);r.addEventListener("load",d);d();\n</script>\n</body>\n</html>\n', _meta: { ui: { prefersBorder: false } } }] }));
43883
+ }, async (uri) => ({ contents: [{ uri: uri.href, mimeType: p, text: '<!doctype html>\n<html lang="en">\n<head>\n<meta charset="utf-8">\n<meta name="viewport" content="width=device-width, initial-scale=1">\n<title>Perfboard board</title>\n<style>\n :root { color-scheme: light dark; font-family: system-ui, sans-serif; font-size: 14px; }\n body { margin: 0; background: transparent; color: CanvasText; }\n figure { margin: 0; display: flex; flex-direction: column; gap: 8px; }\n img { display: block; width: 100%; height: auto; border-radius: 6px; }\n img:not([src]) { display: none; }\n figcaption { display: flex; align-items: center; justify-content: space-between; gap: 12px; flex-wrap: wrap; }\n #caption { opacity: 0.75; }\n button { font: inherit; padding: 6px 12px; border-radius: 6px; border: 1px solid #1f7a3a; background: #1f7a3a; color: #fff; cursor: pointer; }\n button:hover { background: #18602e; }\n button[hidden] { display: none; }\n</style>\n</head>\n<body>\n<figure>\n <img id="board" alt="">\n <figcaption>\n <span id="caption">Drawing the board\u2026</span>\n <button id="open" type="button" hidden>Open in Perfboard Designer</button>\n </figcaption>\n</figure>\n<script type="module">var f="2026-01-26",r=document.getElementById("board"),a=document.getElementById("caption"),u=document.getElementById("open"),i,g=1,s=new Map,o=t=>window.parent.postMessage({jsonrpc:"2.0",...t},"*");function m(t,e){let n=g++;return o({id:n,method:t,params:e}),new Promise(p=>s.set(n,p))}function h(t){let e=t._meta?.board;if(t.isError||!e){a.textContent=t.content?.find(n=>n.type==="text")?.text??"The board couldn\'t be shown.";return}r.src=`data:image/svg+xml;charset=utf-8,${encodeURIComponent(e.svg)}`,r.alt=e.caption,a.textContent=e.caption,i=e.link,u.hidden=!i}window.addEventListener("message",({source:t,data:e})=>{t!==window.parent||e?.jsonrpc!=="2.0"||(e.method===void 0?(s.get(e.id)?.(e.result),s.delete(e.id)):e.method==="ui/notifications/tool-result"?h(e.params??{}):e.id!==void 0&&o({id:e.id,result:{}}))});u.addEventListener("click",()=>{i&&m("ui/open-link",{url:i})});var c=0,l=0;function d(){let t=document.documentElement,e=Math.ceil(t.getBoundingClientRect().height),n=Math.ceil(window.innerWidth);n===c&&e===l||(c=n,l=e,o({method:"ui/notifications/size-changed",params:{width:n,height:e}}))}await m("ui/initialize",{protocolVersion:f,appInfo:{name:"Perfboard Designer board",version:"0.1.1"},appCapabilities:{}});o({method:"ui/notifications/initialized",params:{}});new ResizeObserver(()=>requestAnimationFrame(d)).observe(document.body);r.addEventListener("load",d);d();\n</script>\n</body>\n</html>\n', _meta: { ui: { prefersBorder: false } } }] }));
43869
43884
  K3(server, "show_board", {
43870
43885
  title: "Show board",
43871
43886
  description: "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.",
@@ -44042,7 +44057,7 @@ export interface ProjectFile {
44042
44057
 
44043
44058
  // src/create-server.ts
44044
44059
  function createServer({ editorUrl, imageUrl: imageUrl2, storage }) {
44045
- const server = new McpServer({ name: "perfboard-designer", version: "0.1.0" }, { instructions: INSTRUCTIONS });
44060
+ const server = new McpServer({ name: "perfboard-designer", version: "0.1.1" }, { instructions: INSTRUCTIONS });
44046
44061
  registerCatalogTools(server);
44047
44062
  registerProjectTools(server);
44048
44063
  registerBoardTools(server);
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "perfboard-designer-mcp",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "MCP server for Perfboard Designer: lets AI agents look up parts, check perfboard and stripboard layouts, and hand back a link that opens the board in the editor.",
5
5
  "license": "ISC",
6
6
  "mcpName": "com.perfboarddesigner/mcp",