copper-mcp
Related Servers
Alternatives to copper-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables constrained KiCad layout, autorouting orchestration, ECO revision analysis, and manufacturing evidence packaging through MCP tools and persistent engineering jobs with native DRC/ERC verification.25Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents end-to-end control of KiCad 9+ for rule checks, manufacturing exports, production-readiness certification, and live PCB editor control.MIT
- AlicenseBqualityAmaintenanceAn MCP server that enables AI assistants to analyze schematics, inspect PCBs, trace connections, validate designs, and generate embedded code for KiCad projects.39174MIT
- AlicenseBqualityCmaintenanceProvides schematic/PCB analysis, authoring, and SPICE simulation through MCP, enabling direct KiCad file manipulation and verification without requiring KiCad for reading.18MIT
- AlicenseAqualityCmaintenanceA read-only MCP server for AI agents to understand KiCad projects through progressive disclosure, providing compact summaries and drill-down tools for components, nets, traces, and ERC/DRC checks without blowing context budgets.71MIT
- AlicenseBqualityDmaintenanceMCP server that analyzes, reviews, and exports KiCad 9 designs, with live board editing via IPC and a built-in design-review engine.471MIT
TDQS
Scored across 11 tools
Most tools have clearly distinct purposes, but the three board inspection tools (inspect_board, inspect_board_ir, observe_board_scene) could cause selection ambiguity for an agent looking to simply get board state. Descriptions are detailed, but names alone don't fully disambiguate them.
Predominantly verb_noun with consistent snake_case. Minor inconsistency: 'compare_candidates' is plural while 'validate_candidate' is singular, and 'server_info' is noun_noun instead of verb_noun, but overall pattern is predictable.
11 tools is well within the ideal range and each serves a distinct purpose in the board design workflow, from inspection to candidate preview/apply.
Core route preview/apply, DRC, and board inspection are covered. Placement can only be previewed, not applied, which is a notable but clearly documented gap. There is no direct board editing beyond route application, but the server's stated scope is intentionally limited.