Konnect README

项目的 README,来自 github.com/mixelpixx/Konnect。合并为一个 markdown 文件:README.md。

KiCAD-MCP-Server Logo

Konnect has moved to Konnect-EDA

Go to Konnect-EDA →

This repository is being archived, which makes it read-only. Development continues at Konnect-EDA, from Orchis.ai LLC.

It stays free, unless you're a business

Konnect-EDA is now commercial and closed source. Here's what that means for you:

Business licenses pay for the work, and that's what lets us keep it free for everyone else.

Nothing here is being taken away. The code and releases in this repository stay available under the AGPL-3.0. The original KiCAD MCP Server stays open source under the MIT license and is still maintained. The boards you design are always yours.

Where to go now

Thank you to everyone who built Konnect with us.


AI-assisted PCB design for KiCAD 10. Konnect is a native KiCAD plugin — a single Rust binary — that lets Claude and other AI assistants design schematics and PCBs through the Model Context Protocol (MCP).

228 tools across 21 on-demand toolsets. Schematic capture, PCB layout and routing, ERC/DRC, design-review audits, JLCPCB part search, reference circuits, and a full manufacturing export pipeline — with bundled skills and agents that teach Claude KiCAD conventions out of the box.

Why Konnect exists

Konnect is the successor to KiCAD-MCP-Server, a Python/TypeScript project that proved AI-driven PCB design works — and, in the process, showed exactly where that architecture runs out of road. Konnect was built to fix those specific problems:

The call path was too long. In the original server, a single tool call travels through TypeScript, schema validation, a spawned Python subprocess, JSON over stdin/stdout, a command router, and finally SWIG-generated C++ proxy objects before anything touches your board. That's four language and serialization boundaries, each with its own failure modes — subprocess lifecycle management, stdout parsing that filters out warnings KiCAD leaks into the stream, chunked-JSON reassembly. In Konnect, a tool call is a function call. One process, one language, no plumbing.

The dependency surface was enormous. Running the original means carrying Node.js and its npm tree, Python and its pip packages, wxPython, kicad-skip, and KiCAD's SWIG bindings — two package ecosystems plus a binding layer, every one of them a moving target that can break an install. Konnect is a single static binary — 20–25 MB depending on platform, a ~9 MB download. There is nothing to install alongside it and nothing to version-match.

SWIG is a dead end. The original's PCB backend depends on KiCAD's SWIG Python bindings, which KiCAD is deprecating in favor of its IPC API. SWIG also carried real operational scars: a zone-fill call that can segfault the backend, proxy-object comparison bugs, and a fallback path that can silently swap backends mid-session. Konnect talks to KiCAD 10 through the official IPC API (protobuf over NNG) — the interface KiCAD is investing in — with real-time board edits that integrate with KiCAD's own undo/redo.

Schematic edits should not corrupt files. Konnect edits .kicad_sch files through its own S-expression engine with atomic writes (write, fsync, rename), UUID preservation, and round-trip tests — no third-party schematic library with known gaps, no text-manipulation workarounds.

Context economy is a feature. Exposing all 228 tools to an LLM costs roughly 23K tokens of context on every listing. Konnect's router loads a starter kit (~2K tokens) and lets the model pull in toolsets on demand — plus built-in observability (get_recent_calls, server_stats, JSONL call logs) so the model can diagnose its own tool failures.

The result is smaller, faster to install, aligned with where KiCAD is going, and built for production use rather than experimentation. The original project remains open, maintained, and useful — see the comparison below.

What it does

Instead of describing changes and applying them by hand, the AI works your project directly:

The full tool catalog is documented in tool-directory.md.

How it works

Layer Mechanism
Schematic editing Direct .kicad_sch S-expression editing with atomic writes (no KiCAD required)
PCB editing KiCad 10 IPC API (NNG + protobuf) — real-time and undo-aware; single-footprint placement has a safe headless fallback
Specctra routing Revision-bound Rust DSN export, local Freerouting MCP routing, and strict one-transaction SES import; an authenticated KiCad 10 native-export bridge is explicit opt-in
Exports & checks kicad-cli subprocess (Gerber, PDF, ERC, DRC, …)
Transport MCP JSON-RPC over stdio (default), or Streamable HTTP (transport = "http" / "both")

Explore the request path and safety boundaries in the interactive architecture diagrams. They are published from a standalone documentation repository and add no dependencies to Konnect.

Installation

  1. Download the package for your OS from Releases: konnect-pcm-v<version>-windows.zip, -macos.zip, or -linux.zip. Each bundles that platform's server binary — the macOS package is a universal build, so one download covers Apple Silicon and Intel. (The konnect-pcm-* assets are the KiCAD plugin packages; the other archives are standalone server binaries.)
  2. Open KiCAD 10 → Plugin and Content Manager
  3. Click Install from File and select the zip
  4. Restart KiCAD

Verify: open the PCB Editor → Tools → External Plugins → you should see Konnect.

For KiCad 10, the Konnect settings dialog also offers an optional native Specctra bridge. When enabled, export_specctra_dsn can ask the active PCB Editor to generate its native DSN while Konnect still binds the export to the exact IPC snapshot and creates the strict reverse manifest used during SES import. The bridge is local-only, authenticated, disabled by default, and not the KiCad 11 integration path. Konnect uses its Rust exporter by default; native_bridge_mode: "prefer" enables fallback to Rust when the bridge is unavailable, while "require" refuses instead.

For end-to-end autorouting, run check_freerouting, then export_specctra_dsn → route_specctra_dsn → plan_specctra_ses_import / apply_specctra_ses. Readiness reports engine discovery, native-MCP compatibility, and complete bridge availability separately. The owned Java child is loopback-only and is reaped on success, failure, timeout, or cancellation. The first supported profile preserves fixed straight tracks and through vias; unlocked routing, arcs, zones, and unsupported geometry are rejected before mutation.

Build from source

# protoc is required (protobuf code generation), and cmake (the nng crate
# compiles the NNG C library with it).
# Windows: choco install protoc cmake
# macOS:   brew install protobuf cmake
# Linux:   apt install protobuf-compiler cmake
cargo build --release -p konnect

Install guidance for your AI client

Konnect bundles shared KiCad skills for Claude and Codex. Select the client when installing, checking, or removing that guidance:

# Existing behavior remains the default: Claude skills, agents, and hooks
konnect init

# Codex installs only the shared skills under ~/.agents/skills
konnect init --client codex
konnect status --client codex
konnect uninstall --client codex

MCP server startup never installs or restores guidance. Run konnect init explicitly when you want those files installed; after konnect uninstall, starting the server leaves them removed.

Guidance written by an older konnect init is not updated by upgrading the binary. konnect status compares every installed skill, agent, and hook with the bundle in the binary you run and marks each current, different, or missing. The server makes the same check once for each installed version: the first start after konnect init compares the files, records the result in ~/.konnect, and adds a one-line notice to its initialize instructions if guidance is out of sync. Later starts reuse that record, so guidance you chose to keep is not reported again. get_installation_info shows the result. Re-run konnect init to update it. It overwrites differing files, so keep a copy of any file you edited. --client remains accepted in server commands for compatibility. For example, register a standalone binary with the Codex CLI using:

codex mcp add konnect -- /path/to/konnect --client codex

Claude remains the default when --client is omitted. The installer tracks the two clients independently, and a Codex install does not create or modify ~/.claude.

--help on any subcommand prints that subcommand's usage and writes nothing — konnect init --help describes the installer rather than running it. An argument Konnect does not recognise is an error rather than being ignored, so a typo such as --cleint codex stops instead of quietly installing for the default client.

To verify which Konnect process an MCP client is actually using, call the always-visible get_installation_info tool. It reports the serving build, executable path, verified installation source when one can be proven, KiCad CLI and IPC detection, and restart guidance. A missing build commit or an unknown installation source means the available evidence was insufficient; it is not silently guessed from a directory name.

macOS

The Releases page ships standalone server binaries for both Apple Silicon (aarch64-apple-darwin) and Intel (x86_64-apple-darwin). They are not yet code-signed, so if you download one through a browser, clear the quarantine flag before first launch:

tar xzf konnect-v*-aarch64-apple-darwin.tar.gz
xattr -d com.apple.quarantine ./konnect   # only needed for browser downloads
./konnect --help

Or build from source as above (verified on Apple Silicon; the same target/release/konnect binary is the MCP server).

KiCad on macOS keeps its tools inside the app bundle and they are not on PATH, so point Konnect at them in ~/Library/Application Support/konnect/config.toml:

kicad_cli = "/Applications/KiCad/KiCad.app/Contents/MacOS/kicad-cli"
kicad_binary = "/Applications/KiCad/KiCad.app/Contents/MacOS/kicad"
# KiCad 10's IPC socket on macOS (enable it in KiCad:
# Preferences → Plugins → "Enable KiCad API")
ipc_address = "ipc:///tmp/kicad/api.sock"

Claude Desktop's config lives at ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "konnect": {
      "command": "/path/to/konnect"
    }
  }
}

For Claude Code, put the same snippet in a .mcp.json in your project root.

The macOS PCM package (konnect-pcm-v<version>-macos.zip) bundles a universal server binary, so one download covers Apple Silicon and Intel. The schematic viewer compiles and launches on macOS (Tauri 2 uses the system WKWebView — WebView2 is only a Windows requirement) but hasn't had the same mileage as the Windows build yet.

Setup with Claude Desktop

After a PCM install, the server binary lives in your KiCAD documents folder:

C:\Users\<YOU>\Documents\KiCad\10.0\3rdparty\plugins\com_github_mixelpixx_konnect\bin\konnect.exe

Edit %APPDATA%\Claude\claude_desktop_config.json:

{
  "mcpServers": {
    "konnect": {
      "command": "C:\\Users\\<YOU>\\Documents\\KiCad\\10.0\\3rdparty\\plugins\\com_github_mixelpixx_konnect\\bin\\konnect.exe"
    }
  }
}

Restart Claude Desktop and the Konnect tools appear. For Claude Code, drop the same snippet into a .mcp.json in your project root (see examples/).

Schematic viewer

A standalone viewer that auto-refreshes as the schematic file changes:

schematic-viewer.exe path\to\your\root_schematic.kicad_sch

Point it at the root sheet of a hierarchical design and every sub-sheet is rendered too, with a depth-indented sheet selector in the toolbar. Edits saved from KiCAD (or made by the AI through the schematic tools) re-render only the sheets that changed and refresh the view live — rendering runs against temp-folder snapshots, so the viewer never blocks KiCAD from saving. Pan with click-drag, zoom with the wheel, 0 to fit, R to refresh, drag-and-drop to open a different file. Also launchable by the AI via the open_schematic_viewer tool.

Needs the WebView2 runtime (pre-installed on Windows 10/11) and a KiCAD install for kicad-cli (auto-discovered, or pass --kicad-cli <path>). Built separately from the main workspace — see DEV.md for build steps.

Requirements

License: free for the little guys

Konnect is licensed under the GNU AGPL-3.0.

If you're a hobbyist, student, freelancer, or open-source project: use it freely, no strings attached. Design boards, ship them, sell them.

If you're a business: the AGPL requires that anything you build on or around Konnect — including software provided over a network — be open-sourced under the same license. If that doesn't work for you, commercial licenses are available: see COMMERCIAL.md.

Relationship to KiCAD-MCP-Server

The original Python/TypeScript project remains fully open (MIT) and maintained. Konnect is where new development happens — the architecture it proved, rebuilt for production:

KiCAD-MCP-Server Konnect
Runtime Node.js + Python + SWIG bindings Single static binary (20–25 MB)
Tool call path TS → subprocess → Python → SWIG C++ Direct function call
PCB backend SWIG (deprecated by KiCAD) + experimental IPC KiCAD 10 IPC API
Schematic backend kicad-skip + custom loaders Native S-expression engine, atomic writes
Context cost Router pattern Load/unload toolsets + observability
Skills / agents — 6 skills + 2 agents bundled
License MIT AGPL-3.0 + commercial

Troubleshooting

Plugin doesn't appear in KiCAD — install via the Plugin and Content Manager (not manual copy), then restart KiCAD.

PCB tools return "KiCAD must be running with the board loaded" — open KiCAD with that board first; most PCB tools talk to the running PCB editor. Only an unreachable KiCAD produces that message: if KiCAD is running and the tool refuses anyway, the error is the tool's own reason for refusing. place_component, move_component, rotate_component, and (on KiCAD 10.0.6+) flip_component can fall back to a closed board file when no KiCAD process is reachable. An older, reachable KiCAD makes flip_component refuse rather than silently editing the file underneath it.

See docs/TROUBLESHOOTING.md for socket setup, tools that don't appear after load_toolset, and transaction recovery.

"kicad-cli not found" — common install paths are auto-detected; set the path explicitly in the plugin settings dialog, in a settings.json beside the binary, or in a konnect.toml in the working directory. (A file under any other name works only when passed with --config.)

Support

Konnect (mixelpixx/Konnect)

正在搜索数据库…

1.5K ·GitHub
已归档
这是什么?Konnect 是一个原生 KiCAD 插件,也就是一个 Rust 二进制文件,能让 Claude 和其他 AI 助手通过模型上下文协议(MCP)设计原理图和印制电路板(PCB)。它提供 217 个以上用于原理图、布局、布线和生产制造的工具。
这是独立应用,还是要接入 KiCAD?它是一个插件,以单个静态链接的 Rust 二进制文件形式发布(约 20-25MB),由 KiCAD 加载运行。它通过 KiCAD 10 官方的 IPC API 直接与 KiCAD 通信,而不是作为独立程序单独运行。
我该怎么安装 Konnect?从 Releases 页面下载适用于你操作系统的安装包,然后在 KiCAD 10 中打开 Plugin and Content Manager,点击“Install from File”,选择 zip 文件,并重启 KiCAD。你也可以从源码自行构建。
使用 Konnect 之前,我需要先安装好什么?你需要安装 KiCAD 10(自带 kicad-cli)。大多数 PCB 工具要通过 IPC API 运行,因此还需要先打开目标电路板。然后,将你的 MCP 客户端(Claude Desktop、Claude Code、Codex、VS Code 等)指向 Konnect 的二进制文件。
它能在所有平台上投入生产环境使用吗?该项目明确标注为测试版:核心工具链可以正常工作,但尚未经过大规模的实际使用检验。Windows 是测试最充分的平台;Linux 可以编译并通过 CI 测试,但尚未进行各平台的质量测试;macOS 的二进制文件没有进行代码签名。
它能在 macOS 和 Linux 上用,还是只能在 Windows 上用?三个平台都支持:Windows 是测试最充分的平台;macOS 可以通过发布的二进制文件或从源码构建使用(为 Apple Silicon 和 Intel 提供通用二进制文件);Linux 可以编译并通过 CI 测试,但尚未进行同等的各平台质量测试。
为什么要做 Konnect,而不直接用原版的 KiCAD-MCP-Server?Konnect 用一个 Rust 二进制文件取代了原本缓慢的 Python/TypeScript/SWIG 调用链。它直接与 KiCAD 10 自带的 IPC API 通信,减少了安装复杂度和故障点,同时仍向 LLM 提供数百种 PCB 设计工具。
实时原理图查看器是做什么用的?它是一个独立应用,会在 .kicadsch 文件变化时自动刷新,让你实时看到 AI 的编辑过程。它支持平移和缩放,并能渲染层级式的多页原理图设计。
Nimrod 是什么?它和 Konnect 有什么关系?Nimrod 是同一团队开发的另一个网页调研 MCP 服务器。在设计过程中,它会为 Konnect 提供元件的实时库存情况、数据手册和勘误信息,而不必依赖 AI 过时的训练数据。
Konnect 能帮我为设计搜索真实有货的元件吗?可以。它内置了本地 JLCPCB 元件库搜索功能(包含 250 万个元件),AI 在设计时就能直接查找有货的元件,并推荐替代型号。
作者
mixelpixx
大小
6.4 MB
星标
1.5K
时长
4个月
提交 · 90 天