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
    B
    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
    129
    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.
    22
    50 npm
    11
    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
    199 PyPI
    8
    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
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

A4.1/5.0

Scored across 34 tools

Disambiguation5/5

Every tool has a clearly distinct target resource and action, with cross-references in descriptions to prevent confusion (e.g., read_pcblib vs get_component vs list_components vs search_components). Even overlapping operations like update_component, update_pad, update_primitive, and batch_update are explicitly scoped.

Naming Consistency4/5

The dominant verb_noun pattern is consistent and readable, but there are minor deviations: read_pcblib/write_schlib/write_libpkg use concatenated names instead of underscores, component_exists reverses the order, and bulk_rename/batch_update use adjective prefixes. Overall still predictable.

Tool Count2/5

34 tools is well above the 25-tool threshold for a heavy surface. While each tool has a distinct purpose and the domain is broad, the count risks overwhelming agents and some consolidation (e.g., merging read_pcblib/read_schlib into one parameterized tool) would improve navigability.

Completeness5/5

The tool set provides thorough coverage for Altium library management: read/write for PcbLib and SchLib, full component CRUD, copy/rename/delete/reorder, bulk operations, validation, repair, diff/compare, merge, export/import, backup/restore, 3D model extraction, and symbol parameter/footprint-link management. No obvious dead ends for library authoring workflows.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources