Copper for KiCad
Capped at 90: 2 of 3 real tool calls passed in our test; the tests add up to 95. Why scores are capped
Test points add up to 95; the score is capped at 90 because not every real tool call passed. Not a quality or security rating. Why scores are capped
Test points before the cap (95/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs10/15
- License10/10
New / early find
New / early find: first tested 2026-11-14 UTC. Copper (npm copper-kicad 1.1.1, MIT; repo claynicholson/copper-kicad-mcp, 72 GitHub stars when tested, created 2026-11-12 UTC; not on mcp.so or Glama when checked, PulseMCP blocked our check) lets an MCP client design KiCad boards: schematic, LCSC/JLCPCB parts, PCB placement and routing, fab export. Installed with scripts off; initialize and tools/list over stdio succeeded with no credentials (31 tools). Our test box has no KiCad installed, which the README lists as a prerequisite. Real calls: parts_search {query:'NE555 timer'} returned 8 LCSC results, parts_get {lcsc:'C7593'} returned the NE555DR detail with JLC stock; project_create returned KICAD_NOT_FOUND. copper_status (setup check, does not count) reported KiCad not found. Schematic/PCB tools not tested (need KiCad).
Tool-call test (2026-11-14 UTC, direct MCP stdio client, no LLM): partial. 2 of 3 real calls passed (copper_status setup check not counted); project_create failed because KiCad is not installed. Schematic/PCB tools not tested (need KiCad). Evidence: local test run, Nov 14, 2026 UTC.
Transport (tested 2026-11-14 UTC): stdio
Token cost (estimate): approx. 12610 tokens, cl100k estimate (31 tools, measured 2026-11-14 UTC, version 1.1.1). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 8 read, 9 write (state-changing), 14 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
board_build— write (state-changing)checkpoint— write (state-changing)copper_help— unclassifiedcopper_status— readdesign_review— readexport— unclassifiedfab_export— write (state-changing)focus— unclassifiedlibrary— unclassifiedparts_alternatives— unclassifiedparts_get— readparts_import— unclassifiedparts_search— readparts_source_bom— write (state-changing)pcb_edit— write (state-changing)pcb_place— unclassifiedpcb_pour— write (state-changing)pcb_read— readpcb_route— unclassifiedpcb_route_guided— unclassifiedpcb_route_plan— readpcb_setup— unclassifiedpcb_sync— write (state-changing)project_create— write (state-changing)project_open— unclassifiedproject_summary— readrender— unclassifiedsch_apply— write (state-changing)sch_read— readsch_tidy— unclassifiedverify— unclassified
handshake and tools listed without a recorded key or OAuth
Score 90/100 · Tools 31 · Token cost approx. 12,610 tokens · Compare · Last tested 2026-11-14 UTC · Version tested 1.1.1 · Package copper-kicad · Repo claynicholson/copper-kicad-mcp
Summary: Copper for KiCad completed an MCP handshake without credentials and exposed 31 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 31
- Context cost
- approx. 12610 tokens, cl100k estimate (31 tools, measured 2026-11-14 UTC, version 1.1.1; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-14 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install copper-kicad (Node 20, Linux) succeeded in 0s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 31 tools listed in 0.5s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 72 GitHub stars. |
| docs | partial | 10 | install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 12610 tokens, cl100k estimate for 31 tools · about 154% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-14 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 31 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-14 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
0d6ddfcea5a8: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "copper-kicad",
"version": "1.1.1",
"registry": "npm",
"status": "working",
"tested": "2026-11-14",
"tools_count": 31,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install copper-kicad` (Node 20, Linux) succeeded in 0s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 31 tools listed in 0.5s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 72 GitHub stars."
],
"docs": [
"partial",
10,
"install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y copper-kicad
Pin the version we tested
npx -y copper-kicad@1.1.1
tested 2026-11-14 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"copper-for-kicad": {
"command": "npx",
"args": [
"-y",
"copper-kicad@1.1.1"
]
}
}
}Tools listed
copper_status, project_create, project_open, project_summary, checkpoint, copper_help, sch_apply, sch_read, sch_tidy, library, parts_search, parts_get, parts_import, parts_source_bom, parts_alternatives, verify, design_review, render, pcb_read, pcb_sync, pcb_setup, pcb_place, pcb_route, pcb_pour, pcb_edit, pcb_route_plan, pcb_route_guided, focus, fab_export, export, board_build
Quick config
{
"mcpServers": {
"copper-for-kicad": {
"command": "npx",
"args": [
"-y",
"copper-kicad"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install copper-kicad(Node 20). This is the exact command we ran on 2026-11-14 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (31 in our test).
{
"mcpServers": {
"copper-for-kicad": {
"command": "npx",
"args": [
"-y",
"copper-kicad"
]
}
}
}Test history
- 2026-11-14 UTC: New
Related: Best design MCP servers
FAQ
Is Copper for KiCad deprecated?
No. copper-kicad was not deprecated or archived when we last tested it on 2026-11-14 UTC.
What replaces Copper for KiCad?
Nothing; Copper for KiCad is not deprecated as of 2026-11-14 UTC.
Does Copper for KiCad need an API key?
No. It completed an MCP handshake with no credentials and listed 31 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.