kicad-copilot
Related Servers
Alternatives to kicad-copilot
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server providing full control over KiCad 10, enabling PCB editing, schematic editing, design data, and production output via natural language.MIT
- AlicenseBqualityBmaintenanceAn MCP server that enables AI assistants to analyze schematics, inspect PCBs, trace connections, validate designs, and generate embedded code for KiCad projects.39129MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for creating, modifying, and analyzing KiCAD schematic files using natural language.20MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for controlling KiCad EDA software, enabling schematics, PCB design, manufacturing outputs, design checks, and library management through any MCP-compatible AI assistant.MIT
- FlicenseNot gradedqualityAmaintenanceAn MCP server that enables language models to design real KiCad electronic schematics from plain-language descriptions, placing parts, wiring nets, and running KiCad's electrical rules check to produce editable .kicad_sch files.2-
- AlicenseNot gradedqualityCmaintenanceAn 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
TDQS
Scored across 22 tools
Each tool targets a distinct operation: schematic editing, project queries, checkpoint management, and PCB layout/routing phases. The wait/cancel pairs for long-running operations are clearly separated from the operations themselves, and no two tools appear to perform the same task.
All tool names follow a consistent verb_noun snake_case pattern (e.g., get_schematic, save_checkpoint, auto_route_pcb). Even compound verbs like auto_route and pour_pcb_layers maintain the convention, and wait_/cancel_ prefixes are systematically used for async operations.
At 22 tools, the count is on the higher end, but the server spans three major subdomains (schematic, project/checkpoints, PCB layout/routing), and each tool addresses a concrete need. The count is slightly above the 'ideal' range but not excessive for this scope.
The toolset covers schematic retrieval and modification, project inspection, checkpointing, and a full PCB workflow from layer setup to routing and copper pour. Minor gaps exist (e.g., no direct manual editing of individual tracks or component placements), but the automated workflow is well-covered and agents can work around these limitations.