Skip to main content
Glama

Related Servers

Alternatives to KiCad MCP Pro

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables AI assistants like Claude to interact with KiCAD for PCB design automation.
      58 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      KiCAD MCP is a Model Context Protocol (MCP) implementation that enables Large Language Models (LLMs) like Claude to directly interact with KiCAD for printed circuit board design.
      58 npm
      2,218
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      AI-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.
      22
      50 npm
      11
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to interact with KiCAD for PCB design automation, providing comprehensive tool schemas and real-time project state access.
      58 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      KiCad 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.
      91
      MIT

    TDQS

    C2.7/5.0

    Scored across 241 tools

    Disambiguation3/5

    Most tools have clear category prefixes and distinct purposes, but there are deliberate aliases (pcb_add_zone/pcb_add_copper_zone, export_3d_step/export_step, route_tune_length/tune_track_length) and overlapping clusters around routing, auto-placement, part search, and quality gates. Descriptions help, but at 241 tools misselection becomes likely.

    Naming Consistency4/5

    Tool names generally follow a predictable category_verb_noun snake_case pattern, such as pcb_get_*, sch_add_*, export_*, and vcs_*. Minor deviations like run_drc, get_board_stats, and a few backward-compatible aliases prevent a perfect score, but the overall style is consistent.

    Tool Count1/5

    241 tools is an extreme count for a single MCP server, even for a broad EDA workflow. It creates a heavy selection burden on agents and should likely be split into category-focused servers.

    Completeness4/5

    The server covers the full design lifecycle: project creation, schematic entry, libraries, PCB layout, routing, SI/EMC/PDN, simulation, quality gates, exports, manufacturing, and VCS. Minor gaps exist around generic schematic deletion/update operations, such as removing labels or sheets, but agents can generally work around them.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues