原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

KiCad Schematics and PCBs

作者:unmateria版本 0.2.8i★ 4i在你的电脑上运行代码仓库 ↗
注册名称io.github.unmateria/mcp-kicad

安装方法

What it does

Design KiCad schematics and routed PCBs by talking to Claude. Checked by KiCad. Needs KiCad 10.

  • Connects 在你的电脑上运行
  • Account or key No key needed
  • Category 设计、图片与音频

可搭配使用

教 AI 做这类工作的 Skill,可与本项一起使用

impeccable

The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.

作者:pbakaus★ 113,0421 个 skill

Skill · 操作手册

diagram-design

Editorial diagram design for Claude Code, Codex, GitHub Copilot, Cursor, Factory Droid, Qoder, and Pi. 45 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.

作者:cathrynlavery★ 68,2961 个 skill

Skill · 操作手册

frontend-slides

Create beautiful slides on the web using a coding agent's frontend skills

作者:zarazhangrui★ 32,5791 个 skill

Skill · 操作手册

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度8/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分20/100

质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 2/3 项检查 · 在你的电脑上运行

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude,但需要先准备

不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

  1. 下载开发者的安装文件

    下载作者的 .mcpb 文件

    .mcpb 文件直接来自开发者,我们没有修改

  2. 双击文件,然后在电脑版 Claude 应用中点击 Install

  3. 试一试

    用 KiCad Schematics and PCBs 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 KiCad Schematics and PCBs,或回答中出现 KiCad Schematics and PCBs 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 KiCad Schematics and PCBs

KiCad Schematics and PCBs 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器

你可以改用这些方式

A · 使用能连接 KiCad Schematics and PCBs 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

B · 设计、图片与音频 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 KiCad Schematics and PCBs

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 KiCad Schematics and PCBs 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

Cursor 暂时无法连接 KiCad Schematics and PCBs

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 KiCad Schematics and PCBs 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

VS Code 暂时无法连接 KiCad Schematics and PCBs

开发者只提供了电脑版 Claude 应用的安装文件

你可以改用这些方式

A · 使用能连接 KiCad Schematics and PCBs 的应用

  • 不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 KiCad Schematics and PCBs 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
许可证i
未注明许可证
连接方式
在你的电脑上运行
最新版本i
0.2.8
发布到注册中心i
2026年11月12日
代码最后更新i
2026年11月12日
作者
unmateria
软件包
mcpb: …/mcp-kicad.mcpb
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 unmateria 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于7天前

  • ! 注意

    有许可证

    GitHub 无法识别许可证类型;请打开文件自行查看

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

已公开的漏洞(OSV.dev)

未检查:只能检查标明版本的 npm 和 PyPI 包

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/unmateria-mcp-kicad.svg)](https://mcp.popnx.com/en/servers/unmateria-mcp-kicad)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“设计、图片与音频”中的其他服务器比较i

  • 星标数多于此分类中其他 3303 个服务器的 90%
  • 发布到注册中心的时间比此分类中其他 3303 个服务器的 82% 更新
  • 基础检查结果等于或优于此分类中其他 3303 个服务器的 51%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

KiCad Schematics and PCBs 安全吗?

它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于7天前,最新版本(0.2.8)于7天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。

有什么可以替代它?

同一分类中有:HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Pascal 3D Editor

Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.

作者:pascalorg广泛使用↓ 1037/周★ 2.6万 整个仓库的星标昨天更新

电脑或云端✓ 服务方 · pascal.app

draw.io

Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.

作者:jgraph广泛使用★ 5854前天更新

在云端运行✓ 服务方 · draw.ioPopNx 团队已实际试用

Figma MCP Server

The Figma MCP server brings Figma design context directly into your AI workflow.

作者:figma广泛使用★ 221113个月前更新

在云端运行✓ 服务方 · mcp.figma.com
与相似项目对比
本项
KiCad Schematics and PCBs
HyperFrames by HeyGenPascal 3D Editordraw.ioFigma MCP ServerRemocn: Remotion MCP server
运行位置需要安装在电脑上在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否是否否是否
基础检查2/34/45/54/44/44/4
许可证NOASSERTIONApache-2.0MITApache-2.0–MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

MCP-KiCad

Design electronic schematics and boards by talking to Claude. This is an MCP server that lets a language model draw real KiCad schematics — placing parts, wiring nets, adding power symbols and running KiCad's own electrical rules check — turn them into placed and routed two-layer boards, and hand you the files to open, edit and send to a board house.

*Léeme en español*

An LM2596 step-down converter. Nobody drew this by hand: it was compiled from a text description, and it passes ERC.


What it actually does

You ask for a circuit in plain language. Claude writes a short declarative description of it and calls one tool, compile_schematic, which turns that description into a finished schematic file.

You: Build me a 555 astable running at about 1 Hz, 5 V supply.

Claude: *[looks up the real pin names of the NE555, writes the design, compiles it]*

Done — 7 components, ERC clean. Here's the preview.

The result opens in KiCad like any other schematic. It is not a picture: it is a real file with a real netlist — and one more call turns it into a board.

What makes the output usable

Generating *something* is easy; generating a schematic a human would accept is not. Every compiled schematic is checked before you see it, and the compiler refuses to emit anything that fails:

GuaranteeHow it is enforced
No wire crosses a wire from a different netA geometric gate re-checks every segment. Offenders become net labels instead
No wire runs through a component bodySame gate, checked against each symbol's real outline
Every declared connection existsThe finished file is re-read and its netlist compared against what you asked for
No accidental extra connectionsThe same check, in reverse — a wire that touches a pin it shouldn't is an error
Power symbols really touch their pinsVerified by physical contact, not by net name
A junction wherever wires meetThe rule was measured across the 115 schematics KiCad ships: a dot where three or more wire ends meet, and where two meet on a pin
KiCad agreeskicad-cli runs ERC on the result and the report comes back with it

If a connection cannot be drawn cleanly, it degrades to a net label rather than producing a wire that lies. The schematic is never silently wrong.

A net crossing *itself* is not one of those cases: it is one net either way, so the wire is cut at the crossing and given a junction rather than being thrown away. Only a genuine conflict with another net costs you a wire.

From schematic to board

Every part comes out of compile_schematic with a footprint that has been checked to exist and to have a pad for each pin — the one you named, the one KiCad's library symbol carries, or a stated default. compile_pcb then builds the board:

The 555 astable as compile_pcb lays it out: parts placed from the schematic, connectors on the edges, tracks on both layers. A ground plane fills the back layer (not drawn, so the tracks show).

ConnectivityRead from the netlist KiCad itself exports, so the board agrees with KiCad's *Update PCB from Schematic*, which keeps working on it
PlacementSeeded from the schematic layout; no overlapping courtyards; decoupling capacitors against their IC's power pin, connectors on the board edge, rotations that shorten the wiring
RoutingTwo layers, 45° tracks, wider tracks for supplies and for any net you name (net_widths, e.g. 2 mm for a heater), a ground plane on the back. Or single-sided for boards made at home (single_sided): through-hole parts, every track on the bottom, wide tracks and pads for a CNC or toner transfer, and a straight wire jumper over the top only where a connection cannot be made. Track width and clearance are yours to set (track_width, power_width, clearance)
CheckingKiCad's DRC with schematic parity. A board that does not implement its schematic, or breaks a rule, is never handed over: the routing is thrown away and the board comes back unrouted, with the reason

export_fabrication writes the Gerbers, drill files, a pick-and-place file, a BOM and a zip ready for a board house — and refuses to while the board fails those checks.

What it does not do
  • It cannot check the parts in your hand. Pinouts and footprints come from KiCad's libraries and the datasheets; a transistor whose maker ordered its legs differently, or a module whose header is not the one in the library, is yours to check before ordering boards.
  • No component invention. It uses KiCad's installed symbol libraries, and find_part / import_part bring in what is missing from external KiCad libraries — verified before installation. If a part exists nowhere, it says so instead of drawing one.
  • Not a simulator. It draws what you describe; it does not tell you whether your circuit is a good idea.

Requirements

KiCad 10Provides kicad-cli, used for ERC and for rendering. Earlier versions are untested.
Claude Desktop or Claude CodeOr any other MCP client.
Go 1.24+Only if you build from source.

Installation

Option A — one click (recommended)

Download `mcp-kicad.mcpb` from Releases and double-click it. Claude Desktop installs it as an extension: no JSON to edit, no paths to type. The bundle carries the Windows, macOS and Linux builds, so the same file works everywhere.

Then skip straight to Checking that it works.

On Apple Silicon the bundled macOS build runs through Rosetta. If you want the native one, take mcp-kicad-darwin-arm64 from Option B instead.

Option B — download a binary
  1. Go to Releases and download the file for your system:
SystemFile
Windows (Intel/AMD)mcp-kicad-windows-amd64.exe
Linux (Intel/AMD)mcp-kicad-linux-amd64
Linux (ARM, e.g. Raspberry Pi)mcp-kicad-linux-arm64
macOS (Apple Silicon)mcp-kicad-darwin-arm64
macOS (Intel)mcp-kicad-darwin-amd64
  1. Put it wherever you like — say C:\Tools\mcp-kicad.exe or ~/bin/mcp-kicad.
  1. On Linux and macOS, make it executable:
   chmod +x ~/bin/mcp-kicad

On macOS the first run is blocked because the binary is unsigned. Allow it with:

   xattr -d com.apple.quarantine ~/bin/mcp-kicad

There is nothing else to install. The binary is self-contained and needs no configuration file: it finds KiCad on its own.

Option C — build from source
git clone https://github.com/unmateria/MCP-Kicad.git

cd MCP-Kicad go build -o mcp-kicad ./cmd/server # add .exe on Windows


Connecting it to Claude

*Not needed if you installed the .mcpb bundle — it registers itself.*

Claude Desktop

Edit the configuration file — create it if it isn't there:

SystemLocation
Windows%APPDATA%\Claude\claude_desktop_config.json
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Linux~/.config/Claude/claude_desktop_config.json

Add the server:

{

"mcpServers": { "kicad": { "command": "C:\\Tools\\mcp-kicad.exe", "args": [] } } }

On Linux or macOS the command is a normal path, "/home/you/bin/mcp-kicad".

Windows note: backslashes must be doubled in JSON (C:\\Tools\\...). A single backslash is the single most common reason the server fails to start.

Then quit Claude Desktop completely and reopen it. Reloading the window is not enough — the server runs as a child process and only starts on a full restart.

Claude Code
claude mcp add kicad -- /path/to/mcp-kicad
Checking that it works

Ask Claude:

Use get_project_info to check the KiCad setup.

You should get back the detected kicad-cli path, the library directories, and the output directory. If it reports that kicad-cli was not found, see Configuration below.


Using it

Just describe the circuit. Be specific about what matters to you — supply voltage, part numbers you want, values you've already chosen — and leave the rest to Claude.

Prompts that work well:

Design a 5 V regulated supply from a 12 V input using an LM7805, with input and output decoupling and a power LED.

Make me an ATmega328P minimal board: 16 MHz crystal with load caps, reset pull-up, ICSP header, and decoupling on both supply pins.

Build a two-transistor astable multivibrator that blinks two LEDs at roughly 2 Hz.

Useful things to ask for afterwards:

  • *"Show me the schematic"* — renders a preview image.
  • *"Export it as PDF"* — through kicad-cli.
  • *"Run ERC"* — KiCad's electrical rules check, with the violations explained.
  • *"Move the decoupling caps closer to U1 and recompile"* — the design source is text, so revisions are cheap.

The generated files land in the output directory (get_output_dir tells you where; set_output_dir changes it).

The design source

Behind the scenes, Claude writes a small JSON document and compiles it. You will rarely need to touch this, but it is worth seeing, because it explains why the results are stable — positions are never given in millimetres, they are anchored pin-to-pin:

{

"version": 1, "project": "led_18650", "sheet": "auto",

"blocks": [ { "name": "led", "symbols": [ { "ref": "BT1", "lib": "Device:Battery_Cell", "value": "18650" }, { "ref": "R1", "lib": "Device:R", "value": "100", "rot": 90, "place": { "pin": "1", "at": "BT1.+", "dir": "up", "cells": 1 } }, { "ref": "D1", "lib": "Device:LED", "value": "LED_RED", "rot": 90, "place": { "pin": "A", "at": "R1.2", "dir": "right", "cells": 3 } } ] } ],

"nets": { "VBAT": ["BT1.+", "R1.1"], "_ANODE": ["R1.2", "D1.A"], "GND": ["D1.K", "BT1.-"] },

"power_nets": { "GND": "power:GND" } }

The first symbol in a block anchors it; every other symbol hangs off a pin of one already placed, a whole number of 2.54 mm grid cells away. That is how a schematic stays on-grid and readable no matter how the model reorders things.

The complete format is specified in internal/tools/design_format.md (the same text the design_guide tool serves to the model), and there are thirteen worked examples in docs/compiler/ — from a two-part LED circuit to a greenhouse controller with 27 components.


Configuration

None is required. The server looks for KiCad in the usual places:

  • Windows — C:\Program Files\KiCad\ \bin\kicad-cli.exe, then PATH
  • Linux — /usr/bin/kicad-cli, /usr/local/bin/kicad-cli, then PATH
  • macOS — /Applications/KiCad/KiCad.app/Contents/MacOS/kicad-cli, then PATH

If your install is somewhere unusual, or you want to change where files are written, copy config.ini.example to config.ini next to the executable and fill in what you need:

[paths]

kicad_cli = /opt/kicad/bin/kicad-cli output_dir = /home/you/schematics libs_root = /home/you/mcp-kicad-libs

[api_keys] mouser = digikey_client_id = digikey_client_secret =

The API keys are optional and buy met

只显示了开头部分;其余内容请在仓库中阅读