Skip to main content
Glama
charlesmmorais

Coppermind

by charlesmmorais
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Coppermind

No user-submitted related servers found.

    Related Servers

    • KiCAD MCP Server

      kankrittapon
      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.
      41 npm
      MIT

    • KiCAD MCP Server

      Avinash1286
      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
      21 npm
      1
      MIT

    • kicad-mcp

      fsbondtec
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language interaction with KiCad projects, schematics, and PCBs, supporting project management, design rule checking, netlist extraction, and datasheet RAG search.
      2
      MIT

    • kschlint

      rashuky
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to lint, render, fix, inspect, and find free space in KiCad schematics and PCBs, providing visual feedback and safe automated text fixes.
      10
      MIT

    • pcb-mcp

      Amagtoto
      A
      license
      A
      quality
      B
      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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most domain tools target distinct actions (create project, add component, create net, connect pins, inspect, commit, rollback), and the meta tools are also separable. The main ambiguities are design_preview vs design_commit, whose descriptions both start with compose/review/ERC, and execute_tool, which sounds like a generic way to run any of the domain tools.

    Naming Consistency3/5

    All names are snake_case, but the verb/object order is inconsistent: project_create, component_add, design_commit, and design_rollback are object-first while connect_pins, create_net, inspect_component, find_symbol, and the meta tools are verb-first. The names are understandable, but there is no single predictable pattern.

    Tool Count4/5

    14 tools is within the typical well-scoped range, so the count is not excessive. It is slightly inflated by five meta/discovery tools that support a routed-tool system rather than directly adding circuit-design capability.

    Completeness3/5

    The core workflow from project creation through net creation, pin connection, review, commit, and rollback is covered. However, there are no granular update/delete/disconnect operations for components or nets, and no project listing/loading beyond creation, so the advertised surface has notable gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources