mcp-server-kicad
Related Servers
Alternatives to mcp-server-kicad
- AlicenseAqualityBmaintenanceMCP server for KiCad 10 that provides live PCB access, file-based schematic handling, symbol search, schematic generation from pinouts, and a Python scripting escape hatch.232MIT
Related Servers
- 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
- 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 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
- AlicenseNot gradedqualityAmaintenanceKiCad MCP Pro is an MCP server for KiCad EDA workflows. It lets AI agents automate schematic and PCB tasks, ERC/DRC validation, DFM review, and manufacturing export.3,544 PyPI94MIT
- AlicenseBqualityAmaintenanceAI-powered MCP server for KiCad that enables creating and modifying schematics, searching components, managing hierarchical projects, generating PCB placement, routing boards locally, and creating copper pours through natural language.2250 npm11MIT
- 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-
TDQS
Scored across 109 tools
Most tools target a distinct resource and action, but the large number of list_* and add_* variants (e.g., add_label vs add_global_label vs add_hierarchical_label; add_wires vs wire_pins_to_net vs connect_pins) creates some potential for misselection. Detailed descriptions mostly resolve the ambiguity, so the confusion risk is limited.
Tool names overwhelmingly follow a consistent verb_noun pattern: list_*, add_*, remove_*, get_*, set_*, create_*, export_*, and run_*. Minor exceptions like is_root_schematic and autoroute_pcb do not break the overall predictability.
109 tools is far beyond the 25+ threshold for a heavy tool set and would likely overwhelm an agent's context and tool-selection accuracy. Even for a broad KiCad domain, the surface could be consolidated into fewer, higher-level operations.
The tool set covers essentially the full KiCad workflow: project creation, schematic editing and ERC, hierarchical design, PCB layout and DRC, library management, autorouting, and diverse export formats. No critical gaps are evident; even PCB creation is handled via update_pcb_from_schematic when a board file is missing.