World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
File I/O and primitive-placement tools so AI assistants can create and manage Altium libraries.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 24/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 36/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use Altium Designer MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Altium Designer MCP or shows a Altium Designer MCP tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Altium Designer MCP yet
Altium Designer MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Altium Designer MCP
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect Altium Designer MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Altium Designer MCP
Cursor cannot connect Altium Designer MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Altium Designer MCP
VS Code cannot connect Altium Designer MCP yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Altium Designer MCP
mcpb: …/altium-designer-mcp.mcpbBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account embedded-society, which owns the repo
Code last changed 2 days ago
Uses GPL-3.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/embedded-society-altium-designer-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 days ago, and the latest version (1.4.0) reached the registry 16 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Altium Designer MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | GPL-3.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
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 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.
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 |
[Client Setup](docs/CLIENT_SETUP.md) — 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](docs/USAGE.md) — what to ask for once it is connected: example
workflows, prompts and tips, identical for every client.
┌─────────────────────────────────────────────────────────────────────────────┐
│ AI-ASSISTED COMPONENT CREATION │ │ │ │ Engineer AI MCP Server │ │ │ │ │ │ │ │ "Create 0603 resistor" │ │ │ │ ├────────────────────────►│ │ │ │ │ │ │ │ │ │ │ AI reasons about: │ │ │ │ │ • IPC-7351B pad sizes │ │ │ │ │ • Courtyard margins │ │ │ │ │ • Silkscreen/symbol style │ │ │ │ │ │ │ │ │ │ write_pcblib(primitives) │ │ │ │ ├─────────────────────────────►│ │ │ │ │ │ Writes │ │ │ │ │ .PcbLib + │ │ │ │ write_schlib(symbol) │ .SchLib files │ │ │ ├─────────────────────────────►│ │ │ │ │◄─────────────────────────────┤ │ │ │ │ { status: "success" } │ │ │ │ │ │ │ │ │ "Done! Footprint │ │ │ │ │ and symbol created" │ │ │ │ │◄────────────────────────┤ │ │ │ │ └─────────────────────────────────────────────────────────────────────────────┘
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](docs/TOOLS.md) — this is the categorised overview.
| 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. |
| 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. |
| Tool | Purpose |
|---|---|
diff_libraries | Compare two library files. |
compare_components | Diff two specific components. |
| 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. |
| 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. |
| 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. |
| Tool | Purpose |
|---|---|
list_backups | List automatic backups. |
restore_backup | Restore from a backup. |
| Primitive | Description |
|---|---|
| Pad | SMD or through-hole pad with designator, position, size, shape, layer (see Pad Shapes below), power-plane thermal relief, and its own polygon-connect style |
| 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), with optional hole contours |
| Text | Text string with font, size, position, layer |
| Fill | Filled rectangle on any layer |
| ComponentBody | 3D model reference (embedded STEP models) |
The shape property on pads controls the copper shape. Use this to indicate pin 1:
| Shape | Value | Usage |
|---|---|---|
| Rectangle | "rectangle" | Pin 1 indicator — use for the first pad to distinguish it visually |
| Rounded Rectangle | "rounded_rectangle" | Default for SMD pads (most common) |
| Round | "round" or "circle" | Circular pads, default for through-hole (both values are equivalent) |
| Oval | "oval" | Oblong pads for constrained spaces |
| Octagonal | "octagonal" | Eight-sided pads (chamfered corners) |
Example — marking pin 1 with a rectangular pad:
{
"pads": [ { "designator": "1", "x": -0.75, "y": 0, "width": 0.9, "height": 0.95, "shape": "rectangle" }, { "designator": "2", "x": 0.75, "y": 0, "width": 0.9, "height": 0.95, "shape": "rounded_rectangle" } ] }
This follows the IPC-7351 convention where pin 1 has a distinct shape (typically rectangular or square corners) while other pads use rounded corners.
| Primitive | Description |
|---|---|
| Pin | Component pin with name, designator, electrical type, orientation |
| Rectangle | Filled or unfilled rectangle (component body) |
| RoundRect | Rounded rectangle with corner radii |
| Line | Single line segment |
| Polyline | Multiple connected line segments |
| Polygon | Filled polygon with border and fill colours |
| Arc | Arc or circle |
| Pie | Filled circular sector (arc geometry plus fill) |
| Image | Embedded or linked raster picture with a bounding box |
| **