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 gradedqualityCmaintenanceAn 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
- AlicenseBqualityAmaintenanceAn MCP server that enables AI assistants to analyze schematics, inspect PCBs, trace connections, validate designs, and generate embedded code for KiCad projects.39174MIT
- 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
- 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.2,568 PyPI155MIT
- 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.102258 npm20MIT
- 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.3-
TDQS
Scored across 109 tools
Most tools target distinct KiCad objects or actions, but several clusters overlap: export_netlist vs export_hierarchical_netlist, add_symbol vs add_lib_symbol, add_wires vs connect_pins vs wire_pins_to_net, and the footprint info/pad/bounds tools. The detailed descriptions help, but with 109 tools an agent still has to choose carefully among similar-sounding operations.
Almost all tools use snake_case with a recognizable verb_noun pattern and clear domain prefixes such as schematic, pcb, and lib. Minor exceptions like no_connect_pin, is_root_schematic, and wire_pins_to_net are still readable and do not break the overall convention.
109 tools is far beyond the practical 3-15 range; although KiCad is a broad domain, many tools are highly granular variants such as separate list_* calls for every schematic item type and separate export helpers. This creates a large discoverability and selection burden.
The surface covers most lifecycle workflows: schematic and PCB editing, ERC/DRC, hierarchy management, libraries, exports, and manufacturing outputs. However, there are dead ends such as adding PCB text, lines, zones, or vias without corresponding remove/modify tools, and no explicit footprint-library creation tool.