Skip to main content
Glama
splice-cad

@splice-cad/mcp

Official
by splice-cad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @splice-cad/mcp

No user-submitted related servers found.

    Related Servers

    • Universal Netlist MCP Server

      IntelligentElectron
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables AI agents to understand and analyze electrical schematics from Cadence and Altium for comprehensive design reviews through natural conversations.
      140 npm
      37
      Apache 2.0

    • mcp-server-kicad

      ProductOfAmerica
      A
      license
      A
      quality
      A
      maintenance
      MCP servers for KiCad schematic, PCB, symbol, footprint, and project automation, enabling AI-assisted electronic design via tools for read/write, analysis, and exports.
      109
      8
      MIT

    • mcp-kicad-sch-api

      circuit-synth
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for creating, modifying, and analyzing KiCAD schematic files using natural language.
      20
      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

    • lambdacad-mcp

      Psalmustrack
      A
      license
      B
      quality
      A
      maintenance
      MCP server that lets AI draw in AutoLISP-capable CAD (reference BricsCAD on Linux) via a file bridge, enabling 2D drafting, 3D solid modeling, and verification with 100 tools.
      128
      2
      Apache 2.0
    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

    A3.8/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools clearly target a distinct resource and action, and the descriptions actively steer agents toward the preferred choice (e.g. PREFER get_plan_summary, PREFER execute_commands). A few pairs could still cause misselection — get_project vs get_plan vs get_plan_summary, get_harness vs get_harness_summary, and the search_* tools vs lookup_part — but the boundaries are explained well enough to recover.

    Naming Consistency4/5

    The set overwhelmingly follows a consistent verb_noun snake_case convention: get_part, create_project, save_plan, search_wires, validate_plan, list_harnesses. Minor deviations include the bare verbs undo/redo and get_live_state, which both gets and sets state despite its get_ prefix.

    Tool Count3/5

    At 28 tools, this sits above the borderline 16-25 range and will feel heavy for an agent to navigate. However, the count is defensible because the tools cluster into four coherent functional areas — parts database, projects/plans, legacy harnesses, and the live WebSocket bridge — with no true duplicates, though it bundles what could plausibly be separate servers.

    Completeness4/5

    Core workflows are solidly covered: part creation with enrichment (lookup_part → create_component), project lifecycle, plan read/summarize/validate, assembly generation, and legacy harness CRUD. The notable gaps are the total absence of delete operations across all resources and no update path for parts, which agents can partially work around via the live state and frontend tools.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources