Skip to main content
Glama

Related Servers

Alternatives to pcb-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to interact with KiCAD for PCB design automation, including schematic editing, component placement, routing, DRC/ERC, and export.
      100
      14 npm
      1
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Enables LLMs to inspect, edit, analyze, and render PCB layouts in real-time using the KiCad IPC API, providing tools for board configuration, footprints, tracks, zones, nets, text, shapes, dimensions, exports, screenshots, and CLI automation.
      100
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with KiCAD for PCB design automation. Users can design PCBs using natural language, including component placement, routing, checks, and export.
      52 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables coding agents to query KiCad project data (components, nets, measurements, DRC/ERC, BOM, renders) and edit open boards live via KiCad's IPC API.
      33
      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.
      52 npm
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to design PCBs in KiCAD through natural language, with transactional preview-verify-commit workflow, undo/redo, and an engineering knowledge base.
      14
      1
      MIT

    TDQS

    A4.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: board info, footprints (list/get/move/edit), nets (list/get connections), tracks (list/create), zones (list/manage), vias (create), stats, and design rules. There is no overlap or ambiguity between tool purposes.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case: list_zones, get_board_info, list_footprints, get_footprint, list_nets, get_net_connections, list_tracks, get_board_stats, get_design_rules, move_footprint, create_track, create_via, manage_zone, edit_footprint. The get_ vs list_ distinction is systematic.

    Tool Count5/5

    14 tools is well within the ideal range for a PCB design server. Each tool serves a clear purpose without redundancy, covering board-level information, component/nets/tracks/zones/vias operations, and design rule queries. The count feels appropriately scoped for the domain.

    Completeness3/5

    The tool surface covers reading board data and performing basic edits (move/edit footprint, create track/via, manage zones), but lacks deletion for tracks and vias, and there is no tool to list or query individual vias. This leaves notable gaps for a full PCB editing workflow, though core inspection and simple modifications are supported.

    Maintenance

    ActivityStale
    ResponsivenessNo issues