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.
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 24/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 36/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 Altium Designer MCP 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Altium Designer MCP,或回答中出现 Altium Designer MCP 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 Altium Designer MCP
Altium Designer MCP 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 Altium Designer MCP 的应用
B · 其他 类中能连接 ChatGPT 的其他服务器
从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的
Claude Code 暂时无法连接 Altium Designer MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Altium Designer MCP 的应用
Cursor 暂时无法连接 Altium Designer MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Altium Designer MCP 的应用
VS Code 暂时无法连接 Altium Designer MCP
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 Altium Designer MCP 的应用
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过 GitHub 账户 embedded-society 验证,该账户拥有此仓库
代码最后更新于前天
使用 GPL-3.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/embedded-society-altium-designer-mcp)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于前天,最新版本(1.4.0)于16天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
| 本项 Altium Designer MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 否 | 否 |
| 基础检查 | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| 许可证 | GPL-3.0 | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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 |
| **