Skip to main content
Glama
embedded-society

altium-designer-mcp

by embedded-society
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to altium-designer-mcp

Related Servers

  • KiCad MCP Server

    Seeed-Studio
    A
    license
    B
    quality
    A
    maintenance
    An MCP server that enables AI assistants to analyze schematics, inspect PCBs, trace connections, validate designs, and generate embedded code for KiCad projects.
    39
    139
    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-copilot

    biosshot
    A
    license
    B
    quality
    A
    maintenance
    AI-powered MCP server for KiCad that enables creating and modifying schematics, searching components, managing hierarchical projects, generating PCB placement, routing boards locally, and creating copper pours through natural language.
    10
    22
    52 npm
    15
    MIT

  • 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
    409 PyPI
    13
    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
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

A4.1/5.0

Scored across 34 tools

Disambiguation4/5

The descriptions are exceptionally clear about when to use each tool, and most tools target distinct operations. However, with 34 tools there are several overlapping pairs (read_pcblib vs export_library, update_component vs write_pcblib, compare_components vs diff_libraries, copy_component vs copy_component_cross_library) that an agent could still confuse despite the guidance.

Naming Consistency5/5

Every tool uses snake_case with a verb_noun structure (read_pcblib, write_schlib, update_primitive, delete_component, etc.). The pattern holds consistently even for longer names like manage_schlib_parameters and copy_component_cross_library, making the tool names highly predictable.

Tool Count2/5

34 tools is well above the typical 3-15 range and the 25+ threshold for 'too many'. Many tools are specialized and could be consolidated (e.g., multiple read/export variants, separate copy/rename/bulk_rename tools), making the surface heavy for the domain.

Completeness4/5

The server covers read, write, update, delete, validate, repair, compare, merge, copy, rename, backup, and 3D model extraction for Altium libraries. Gaps are minor: no fine-grained schematic primitive update (must replace whole symbol via update_component), no IntLib compilation, and SchLib repair is absent, but these are workable around.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources