Skip to main content
Glama
daedalus

mcp-kicad

by daedalus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-kicad

No user-submitted related servers found.

    Related Servers

    • kicad-mcp-kipy

      mnori0211
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for KiCad 10 that enables AI assistants to inspect and control schematics and PCB layouts in real-time using the official kipy Python bindings.
      57 PyPI
      MIT

    • kicad-mcp

      AbdulAzeez0001
      A
      license
      Not graded
      quality
      C
      maintenance
      An 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

    • kicad-mcp

      lucatib
      A
      license
      A
      quality
      B
      maintenance
      MCP 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.
      23
      2
      MIT

    • KiCad MCP Server

      Akhil-Chaturvedi
      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

    • kicad-mcp

      HackInvent
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible assistants to inspect and edit the open PCB in KiCad, including reading board info, footprints, nets, tracks, selection, and BOM data, as well as moving footprints, adding tracks and text, updating BOM fields, and saving the board.
      13
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 41 tools

    Disambiguation5/5

    Each tool targets a distinct action and object (e.g., create_arc vs create_line, list_nets vs list_tracks). Overlaps are minimal and descriptions clarify differences.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., create_arc, list_footprints, get_board_info). No mixing of conventions.

    Tool Count3/5

    41 tools is high, but the domain (PCB design) requires many operations. Some redundancy exists (check_connection vs get_version), and a few tools could be merged (e.g., move_footprint and move_item).

    Completeness2/5

    The toolset covers creation, listing, and basic manipulation but lacks update/modify operations for existing items, no netclass creation, and no design rule checking. Significant gaps for a full PCB workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources