Skip to main content
Glama
Sign In
altium-designer-mcp

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
    177
    MIT

  • KiCad MCP Server

    Akhil-Chaturvedi
    A
    license
    Not graded
    quality
    C
    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
    101 npm
    22
    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
    467 PyPI
    15
    GPL 3.0

  • kicad-mcp

    AbdulAzeez0001
    A
    license
    Not graded
    quality
    D
    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.2/5.0

Scored across 34 tools

Disambiguation5/5

Every tool has a clearly distinct purpose, and many descriptions explicitly cross-reference alternatives (e.g. read_pcblib vs get_component vs export_library; update_component vs update_primitive vs update_pad). The granularity is fine but well-labeled, so an agent can reliably select the right tool.

Naming Consistency4/5

Most names follow a consistent snake_case verb_noun pattern (read_pcblib, write_schlib, copy_component, update_pad), but a few deviate to noun_verb or adjective_verb (component_exists, batch_update, bulk_rename). These exceptions are still readable and do not seriously impair predictiveness.

Tool Count3/5

34 tools is heavy for any MCP server and exceeds the typical 3-15 range. The domain is complex enough to justify many operations, but the surface feels borderline bloated and could likely be consolidated in places (e.g. separate read/write per file type).

Completeness5/5

The set covers full CRUD for both PcbLib and SchLib components, plus library-level import/export, merge, diff, validate, repair, backup/restore, rendering, style extraction, STEP model extraction, and LibPkg generation. No obvious lifecycle gaps remain for an Altium library management server.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources