Lets an AI read, write and edit Altium Designer .PcbLib/.SchLib component libraries byte-exactly.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Documentation Overview
altium-designer-mcp
Let an AI build your Altium libraries — it does the engineering, this tool writes the files.
An MCP server that gives AI assistants (Claude Code, Claude Desktop, Cursor, Antigravity, VS Code Copilot — any MCP client) file I/O
and primitive-placement tools for Altium Designer .PcbLib (footprint) and .SchLib (symbol)
libraries — so the AI can create and maintain any component, not just pre-programmed packages.
The Problem
Building Altium component libraries by hand is slow and repetitive — every footprint means
looking up IPC-7351B pad sizes, courtyards, and silkscreen, then placing each primitive by
hand. AI assistants are excellent at exactly that reasoning, but they cannot write Altium's
binary .PcbLib/.SchLib files — an undocumented OLE compound format that is easy to
corrupt, and Altium silently refuses to open a malformed file.
| Approach | Problem |
|---|---|
| Draw every footprint by hand in Altium | Slow and repetitive; the AI can't touch the file |
| Ask an AI to emit the binary file directly | It produces a corrupt file Altium won't open |
| Pre-programmed footprint generators | Only the package types someone coded in advance |
The Core Idea
The AI handles the intelligence. The tool handles file I/O.
| Responsibility | Owner |
|---|---|
| IPC-7351B calculations | AI |
| Package layout decisions | AI |
| Style choices | AI |
| Datasheet interpretation | AI |
| Reading/writing Altium files | This tool |
| Primitive placement | This tool |
| STEP model attachment | This tool |
This means the AI can create any footprint — not just pre-programmed package types. See docs/VISION.md for the full architectural rationale.
Who Is This For?
Anyone who builds or maintains Altium component libraries and uses an MCP-capable AI
assistant. The AI does the engineering (datasheet → dimensions → style); this server lets it
read and write the actual .PcbLib / .SchLib files.
| If you… | Then… |
|---|---|
| Use Claude Code, Claude Desktop, Cursor, Antigravity, VS Code + Copilot — any MCP client — and design in Altium | ✅ This is for you |
| Want pre-baked generators for a fixed set of packages | ❌ Not this — the point is any component |
| Don't use Altium | ❌ Not applicable |
Quick Start
Client Setup — verified configuration for Claude Code, Claude Desktop, Google Antigravity, Cursor, VS Code, GitHub Copilot CLI, Windsurf, Cline, Roo Code, Kiro, JetBrains, Zed, Gemini CLI, Codex CLI, Continue, Goose, OpenCode and any other stdio MCP client, plus troubleshooting — on Windows, Linux, and macOS.
Using the server — what to ask for once it is connected: example workflows, prompts and tips, identical for every client.
How It Works
MCP Tools
The server exposes 34 tools, working on both .PcbLib (footprints) and
.SchLib (symbols). Every tool's full parameters and examples live in
docs/TOOLS.md — this is the categorised overview.
Read & write
| Tool | Purpose |
|---|---|
read_pcblib | Read footprints from a .PcbLib. |
write_pcblib | Write footprints to a .PcbLib. |
read_schlib | Read symbols from a .SchLib. |
write_schlib | Write symbols to a .SchLib. |
Inspect & visualise
| Tool | Purpose |
|---|---|
list_components | List component names (paginated). |
get_component | Get one component's full data. |
search_components | Search across libraries by regex/glob. |
component_exists | Check whether components exist. |
render_footprint | ASCII-art preview of a footprint. |
render_symbol | ASCII-art preview of a symbol. |
extract_style | Extract styling from an existing library. |
Compare
| Tool | Purpose |
|---|---|
diff_libraries | Compare two library files. |
compare_components | Diff two specific components. |
Edit in place
| Tool | Purpose |
|---|---|
update_component | Update a component, preserving its position. |
update_pad | Update one pad's properties. |
update_primitive | Update one primitive (track/arc/text/fill/region). |
batch_update | Batch updates across all components. |
reorder_components | Reorder components in a library. |
manage_schlib_parameters | List/get/set/remove SchLib parameters. |
manage_schlib_footprints | Manage footprint links in SchLib symbols. |
Manage components
| Tool | Purpose |
|---|---|
delete_component | Delete one or more components. |
copy_component | Duplicate a component within a library. |
rename_component | Rename a component (atomic). |
copy_component_cross_library | Copy a component to another library. |
bulk_rename | Pattern-based multi-rename. |
Library operations
| Tool | Purpose |
|---|---|
merge_libraries | Merge multiple libraries into one. |
write_libpkg | Write a .LibPkg project grouping libraries for IntLib compilation. |
export_library | Export to JSON/CSV. |
import_library | Import from JSON (inverse of export). |
validate_library | Validate for common issues. |
repair_library | Remove orphaned data. |
extract_step_model | Extract embedded STEP 3D models. |
Backups & safety
| Tool | Purpose |
|---|---|
list_backups | List automatic backups. |
restore_backup | Restore from a backup. |
Primitive Types
Footprint Primitives (PcbLib)
| Primitive | Description |
|---|---|
| Pad | SMD or through-hole pad with designator, position, size, shape, layer (see Pad Shapes below) |
| Via | Vertical interconnect with layer span, hole size, and thermal relief |
| Track | Line segment on any layer (silkscreen, assembly, etc.) |
| Arc | Arc or circle on any layer |
| Region | Filled polygon (courtyard, copper pour) |
| Text | Text string with font, size, position, layer |
| Fill | Filled rectangle on any layer |
| ComponentBody | 3D model reference (embedded STEP models) |
Pad Shapes and Pin 1 Indicator
The shape property on pads controls the copper shape. Use this to indicate pin 1:
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Altium Designer MCP
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/altium-designer-mcp)HTML Embed
<a href="https://allmcps.com/mcp/altium-designer-mcp"><img src="https://allmcps.com/api/badge/altium-designer-mcp?style=directory" alt="Altium Designer MCP on AllMCPs" /></a>Technical Specs & Signals
CategoryDeveloper Tools
33Quality signal: Emerging · 33/100How this signal is calculated ▾
Server availabilityNot measured
Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.
Verified ownership10/20
Documentation & tools11/30
Adoption & activity4/15
Community engagement0/10
A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.
Own this project?
This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.
Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.
Claim & get free dofollowShare & Embed
Add our SVG badge (dark/light directory styles) or embeddable widget to your site.