impeccable
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Design KiCad schematics and routed PCBs by talking to Claude. Checked by KiCad. Needs KiCad 10.
この種の作業を AI に教える Skill。これと一緒に使えます
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
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.
Create beautiful slides on the web using a coding agent's frontend skills
一覧は利用スコア(100 点満点)で並びます。内訳は次のとおり
| 人気 | 8/80 | GitHub スターか週間ダウンロード数。大きい方を 60、小さい方を 20 で数えます |
|---|---|---|
| 新しさ | 12/12 | 30 日以内のリリースかコード更新で満点 |
| 応答中 | 0/8 | 前回の確認でクラウドのエンドポイントが応答 |
| 利用スコア | 20/100 |
品質: 基本チェック 2/3 項目に合格(表示のみ、並び順には不使用) · 勢い: データなし (「急上昇」タブでのみ使用)
使っているAIアプリを選んで、設定をコピーしてください。
チェック 2/3 合格 · あなたのパソコンで動きます
まず:どの AI を使っていますか?
使っているアプリを選ぶと、下に手順が表示されます。
Claude につなげますが、先に準備が必要です
キー不要、インストール不要 · パソコン版 Claude アプリ(Windows または Mac)のみ。Web やスマホでは使えません
KiCad Schematics and PCBs を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が KiCad Schematics and PCBs を使っていると言うか、回答に KiCad Schematics and PCBs のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT はまだ KiCad Schematics and PCBs につなげません
KiCad Schematics and PCBs はパソコンに入れて使うものですが、ChatGPT は Web 上で動くサーバーにしかつなげません
A · KiCad Schematics and PCBs につなげるアプリを使う
B · デザイン・画像・音声 の中で ChatGPT につなげる別のサーバー
同じカテゴリでよく使われているものから、キーなしでアドレスだけでつなげるものを選びました
Claude Code はまだ KiCad Schematics and PCBs につなげません
提供元はパソコン版 Claude アプリ用のインストールファイルしか用意していません
A · KiCad Schematics and PCBs につなげるアプリを使う
Cursor はまだ KiCad Schematics and PCBs につなげません
提供元はパソコン版 Claude アプリ用のインストールファイルしか用意していません
A · KiCad Schematics and PCBs につなげるアプリを使う
VS Code はまだ KiCad Schematics and PCBs につなげません
提供元はパソコン版 Claude アプリ用のインストールファイルしか用意していません
A · KiCad Schematics and PCBs につなげるアプリを使う
このサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。
パソコン上で動かせるアプリ
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月19日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント unmateria で確認済みです
コードの最終更新:7 日前
GitHubがライセンスの種類を判別できませんでした。ファイルを開いて確認してください
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/servers/unmateria-mcp-kicad)質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
まだレビューはありません
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック3項目のうち2項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は7 日前、最新バージョン(0.2.8)がレジストリに届いたのは7 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにMCPBも必要です。
同じカテゴリには:HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server
同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
The Figma MCP server brings Figma design context directly into your AI workflow.
Hosted MCP for Remotion videos: search Remocn components, read docs, plan a video, preview it.
| これ KiCad Schematics and PCBs | HyperFrames by HeyGen | Pascal 3D Editor | draw.io | Figma MCP Server | Remocn: Remotion MCP server | |
|---|---|---|---|---|---|---|
| 動く場所 | パソコンにインストールが必要 | クラウドで動き、インストール不要 | クラウドでもパソコンにインストールでも使える | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 | クラウドで動き、インストール不要 |
| キーが必要 | いいえ | いいえ | いいえ | いいえ | いいえ | いいえ |
| Claude で + から追加 | いいえ | はい | いいえ | いいえ | はい | いいえ |
| 基本チェック | 2/3 | 4/4 | 5/5 | 4/4 | 4/4 | 4/4 |
| ライセンス | NOASSERTION | Apache-2.0 | MIT | Apache-2.0 | – | MIT |
| 料金 | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし |
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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.
An LM2596 step-down converter. Nobody drew this by hand: it was compiled from a text description, and it passes ERC.
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.
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:
| Guarantee | How it is enforced |
|---|---|
| No wire crosses a wire from a different net | A geometric gate re-checks every segment. Offenders become net labels instead |
| No wire runs through a component body | Same gate, checked against each symbol's real outline |
| Every declared connection exists | The finished file is re-read and its netlist compared against what you asked for |
| No accidental extra connections | The same check, in reverse — a wire that touches a pin it shouldn't is an error |
| Power symbols really touch their pins | Verified by physical contact, not by net name |
| A junction wherever wires meet | The 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 agrees | kicad-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.
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).
| Connectivity | Read from the netlist KiCad itself exports, so the board agrees with KiCad's *Update PCB from Schematic*, which keeps working on it |
| Placement | Seeded 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 |
| Routing | Two 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) |
| Checking | KiCad'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.
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.| KiCad 10 | Provides kicad-cli, used for ERC and for rendering. Earlier versions are untested. |
| Claude Desktop or Claude Code | Or any other MCP client. |
| Go 1.24+ | Only if you build from source. |
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-arm64from Option B instead.
| System | File |
|---|---|
| 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 |
C:\Tools\mcp-kicad.exe or ~/bin/mcp-kicad. 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.
git clone https://github.com/unmateria/MCP-Kicad.git
cd MCP-Kicad go build -o mcp-kicad ./cmd/server # add .exe on Windows
*Not needed if you installed the .mcpb bundle — it registers itself.*
Edit the configuration file — create it if it isn't there:
| System | Location |
|---|---|
| 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 mcp add kicad -- /path/to/mcp-kicad
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.
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:
kicad-cli.The generated files land in the output directory (get_output_dir tells you where; set_output_dir changes it).
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.
None is required. The server looks for KiCad in the usual places:
C:\Program Files\KiCad\ \bin\kicad-cli.exe, then PATH/usr/bin/kicad-cli, /usr/local/bin/kicad-cli, then PATH/Applications/KiCad/KiCad.app/Contents/MacOS/kicad-cli, then PATHIf 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