Skip to main content
Glama
Copper

Copper

Related Servers

Alternatives to Copper

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to interact with KiCAD for PCB design automation, including schematic editing, component placement, routing, DRC/ERC, and export.
      100
      38 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      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.
      61 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to read and modify KiCAD PCB designs through the KiCAD IPC API, providing tools for board queries, footprint placement, track creation, DRC, and export.
      14
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to turn plain-language requests into complete, routed and design-rule-checked printed circuit boards, including engineering review, part search and inventory use, and export to Gerber, KiCad, BOM and pick-and-place files.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with KiCAD for PCB design automation, including schematic and PCB project state access, component placement, routing, and exports through standardized tools and resources.
      61 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to design and edit PCBs through natural language, including project setup, schematic editing, component placement, custom symbol and footprint generation, routing, DRC/ERC checks, and production file export. It also integrates JLCPCB parts catalog data, Freerouting automation, and visual snapshots for cross-platform Windows, Linux, and macOS workflows.
      61 npm
      MIT

    TDQS

    A4/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools target clearly distinct phases (project, schematic, PCB, parts, export), and descriptions explicitly steer between abstraction levels such as board_build vs individual pcb_* steps or pcb_edit vs pcb_place. A few boundaries still blur: design_review overlaps verify(what='review'), and multiple routing entry points require judgment.

    Naming Consistency4/5

    Names are consistently snake_case with domain prefixes (sch_, pcb_, parts_, project_, copper_, fab_) and mostly action suffixes. Minor deviations are single-word tools (checkpoint, library, render, verify, focus, export) and the noun_noun parts_alternatives.

    Tool Count2/5

    31 tools is heavy for a single MCP server and exceeds the typical 15-tool comfort zone, increasing context and selection overhead. The domain is broad and some tools are justified, but board_build already bundles several pcb_* workflows, so consolidation is possible.

    Completeness5/5

    The surface covers the full KiCad lifecycle: project setup, schematic read/edit, library and part sourcing, PCB sync/place/route/pour/edit, ERC/DRC/review, checkpoints, rendering, and fab/export. No obvious operational gaps appear for PCB design automation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues