Skip to content
Back to search

Konnect

AI-assisted PCB design for KiCAD 10. Native KiCAD plugin — a single Rust binary exposing 217 schematic, layout, routing, placement, design-review, and manufacturing tools to Claude, or the LLM of your choosing

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/mixelpixx--konnect/badge.svg)](/listings/mixelpixx--konnect)

HTML

<a href="/listings/mixelpixx--konnect"><img src="/api/listings/mixelpixx--konnect/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

From the KiCAD Plugin Manager (recommended)

1. Download the package for your OS from [Releases](https://github.com/mixelpixx/Konnect/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

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 400 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <a name="top"></a>
  2. <div align="center">
  3. <img src="resources/images/KiCAD-MCP-Server-rust.svg" alt="KiCAD-MCP-Server Logo" height="240" />
  4. # Konnect has moved to Konnect-EDA
  5. ## [Go to Konnect-EDA →](https://github.com/Orchis-ai-LLC/Konnect-EDA)
  6. </div>
  7. This repository is being archived, which makes it read-only. Development continues
  8. at Konnect-EDA, from Orchis.ai LLC.
  9. ## It stays free, unless you're a business
  10. Konnect-EDA is now commercial and closed source. Here's what that means for you:
  11. - **Everyone, businesses included:** free until version 1.0.
  12. - **Personal, hobby, student and open-hardware work:** still free after 1.0. You'll
  13. need a license key, and that key is free too.
  14. - **Businesses:** a paid license from 1.0.
  15. Business licenses pay for the work, and that's what lets us keep it free for
  16. everyone else.
  17. **Nothing here is being taken away.** The code and releases in this repository stay
  18. available under the AGPL-3.0. The original
  19. [KiCAD MCP Server](https://github.com/mixelpixx/KiCAD-MCP-Server) stays open source
  20. under the MIT license and is still maintained. The boards you design are always yours.
  21. ## Where to go now
  22. - **Downloads:** the [Konnect-EDA releases page](https://github.com/Orchis-ai-LLC/Konnect-EDA/releases).
  23. The first release is coming soon.
  24. - **Bugs and feature requests:** the
  25. [Konnect-EDA issue tracker](https://github.com/Orchis-ai-LLC/Konnect-EDA/issues).
  26. - **Want to help build it?** [Sign up to contribute](https://orchis.ai/konnect/join).
  27. - **Contributed to Konnect?** Please [complete your sign-off](https://orchis.ai/konnect/sign-off)
  28. by November 20.
  29. - **Using it at a company?** See [licensing](https://konnect-eda.orchis.ai/licensing/).
  30. Thank you to everyone who built Konnect with us.
  31. ---
  32. **AI-assisted PCB design for KiCAD 10.** Konnect is a native KiCAD plugin — a single
  33. Rust binary — that lets Claude and other AI assistants design schematics and PCBs
  34. through the [Model Context Protocol](https://modelcontextprotocol.io) (MCP).
  35. **228 tools across 21 on-demand toolsets.** Schematic capture, PCB layout and
  36. routing, ERC/DRC, design-review audits, JLCPCB part search, reference
  37. circuits, and a full manufacturing export pipeline — with bundled skills and agents
  38. that teach Claude KiCAD conventions out of the box.
  39. ## Why Konnect exists
  40. Konnect is the successor to [KiCAD-MCP-Server](https://github.com/mixelpixx/KiCAD-MCP-Server),
  41. a Python/TypeScript project that proved AI-driven PCB design works — and, in the
  42. process, showed exactly where that architecture runs out of road. Konnect was built
  43. to fix those specific problems:
  44. **The call path was too long.** In the original server, a single tool call travels
  45. through TypeScript, schema validation, a spawned Python subprocess, JSON over
  46. stdin/stdout, a command router, and finally SWIG-generated C++ proxy objects before
  47. anything touches your board. That's four language and serialization boundaries, each
  48. with its own failure modes — subprocess lifecycle management, stdout parsing that
  49. filters out warnings KiCAD leaks into the stream, chunked-JSON reassembly. In
  50. Konnect, a tool call is a function call. One process, one language, no plumbing.
  51. **The dependency surface was enormous.** Running the original means carrying Node.js
  52. and its npm tree, Python and its pip packages, wxPython, kicad-skip, and KiCAD's
  53. SWIG bindings — two package ecosystems plus a binding layer, every one of them a
  54. moving target that can break an install. Konnect is a single static binary —
  55. 20–25 MB depending on platform, a ~9 MB download. There is nothing to install
  56. alongside it and nothing to version-match.
  57. **SWIG is a dead end.** The original's PCB backend depends on KiCAD's SWIG Python
  58. bindings, which KiCAD is deprecating in favor of its IPC API. SWIG also carried
  59. real operational scars: a zone-fill call that can segfault the backend, proxy-object
  60. comparison bugs, and a fallback path that can silently swap backends mid-session.
  61. Konnect talks to KiCAD 10 through the official IPC API (protobuf over NNG) — the
  62. interface KiCAD is investing in — with real-time board edits that integrate with
  63. KiCAD's own undo/redo.
  64. **Schematic edits should not corrupt files.** Konnect edits `.kicad_sch` files
  65. through its own S-expression engine with atomic writes (write, fsync, rename), UUID
  66. preservation, and round-trip tests — no third-party schematic library with known
  67. gaps, no text-manipulation workarounds.
  68. **Context economy is a feature.** Exposing all 228 tools to an LLM costs roughly 23K
  69. tokens of context on every listing. Konnect's router loads a starter kit (~2K
  70. tokens) and lets the model pull in toolsets on demand — plus built-in observability
  71. (`get_recent_calls`, `server_stats`, JSONL call logs) so the model can diagnose its
  72. own tool failures.
  73. The result is smaller, faster to install, aligned with where KiCAD is going, and
  74. built for production use rather than experimentation. The original project remains
  75. open, maintained, and useful — see [the comparison below](#relationship-to-kicad-mcp-server).
  76. ## What it does
  77. Instead of describing changes and applying them by hand, the AI works your project
  78. directly:
  79. - **Place and wire schematic components** — add resistors, ICs, connectors; wire them
  80. together by pin name
  81. - **Lay out the PCB** — place, move, rotate, and route footprints in real time via
  82. KiCAD's IPC API, with full undo/redo integration
  83. - **Run design checks** — ERC, DRC, connectivity validation, decoupling audits,
  84. power-rail review, BOM health checks
  85. - **Export production files** — Gerbers, drill, BOM, pick-and-place, 3D models, PDF
  86. - **Search JLCPCB parts** — find in-stock components in a local 2.5M-part catalog and
  87. suggest alternatives
  88. - **Start from reference circuits** — USB-C, LDO, buck converter, STM32, I2C, LED
  89. templates with verified component values
  90. - **Watch it happen** — a live schematic viewer auto-refreshes as the AI edits
  91. The full tool catalog is documented in [tool-directory.md](tool-directory.md).
  92. ## How it works
  93. | Layer | Mechanism |
  94. |-------|-----------|
  95. | Schematic editing | Direct `.kicad_sch` S-expression editing with atomic writes (no KiCAD required) |
  96. | PCB editing | KiCad 10 IPC API (NNG + protobuf) — real-time and undo-aware; single-footprint placement has a safe headless fallback |
  97. | 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 |
  98. | Exports & checks | `kicad-cli` subprocess (Gerber, PDF, ERC, DRC, …) |
  99. | Transport | MCP JSON-RPC over stdio (default), or Streamable HTTP (`transport = "http"` / `"both"`) |
  100. Explore the request path and safety boundaries in the
  101. [interactive architecture diagrams](docs/ARCHITECTURE_DIAGRAMS.md). They are
  102. published from a standalone documentation repository and add no dependencies to
  103. Konnect.
  104. ## Installation
  105. ### From the KiCAD Plugin Manager (recommended)
  106. 1. Download the package for your OS from [Releases](https://github.com/mixelpixx/Konnect/releases):
  107. `konnect-pcm-v<version>-windows.zip`, `-macos.zip`, or `-linux.zip`. Each
  108. bundles that platform's server binary — the macOS package is a universal
  109. build, so one download covers Apple Silicon and Intel. (The `konnect-pcm-*`
  110. assets are the KiCAD plugin packages; the other archives are standalone
  111. server binaries.)
  112. 2. Open KiCAD 10 → **Plugin and Content Manager**
  113. 3. Click **Install from File** and select the zip
  114. 4. Restart KiCAD
  115. Verify: open the **PCB Editor** → **Tools → External Plugins** → you should see
  116. **Konnect**.
  117. For KiCad 10, the Konnect settings dialog also offers an optional **native
  118. Specctra bridge**. When enabled, `export_specctra_dsn` can ask the active PCB
  119. Editor to generate its native DSN while Konnect still binds the export to the
  120. exact IPC snapshot and creates the strict reverse manifest used during SES
  121. import. The bridge is local-only, authenticated, disabled by default, and not
  122. the KiCad 11 integration path. Konnect uses its Rust exporter by default;
  123. `native_bridge_mode: "prefer"` enables fallback to Rust when the bridge is
  124. unavailable, while `"require"` refuses instead.
  125. For end-to-end autorouting, run `check_freerouting`, then
  126. `export_specctra_dsn` → `route_specctra_dsn` →
  127. `plan_specctra_ses_import` / `apply_specctra_ses`. Readiness reports engine
  128. discovery, native-MCP compatibility, and complete bridge availability
  129. separately. The owned Java child is loopback-only and is reaped on success,
  130. failure, timeout, or cancellation. The first supported profile preserves fixed
  131. straight tracks and through vias; unlocked routing, arcs, zones, and unsupported
  132. geometry are rejected before mutation.
  133. ### Build from source
  134. ```bash
  135. # protoc is required (protobuf code generation), and cmake (the nng crate
  136. # compiles the NNG C library with it).
  137. # Windows: choco install protoc cmake
  138. # macOS: brew install protobuf cmake
  139. # Linux: apt install protobuf-compiler cmake
  140. cargo build --release -p konnect
  141. ```
  142. ### Install guidance for your AI client
  143. Konnect bundles shared KiCad skills for Claude and Codex. Select the client when
  144. installing, checking, or removing that guidance:
  145. ```bash
  146. # Existing behavior remains the default: Claude skills, agents, and hooks
  147. konnect init
  148. # Codex installs only the shared skills under ~/.agents/skills
  149. konnect init --client codex
  150. konnect status --client codex
  151. konnect uninstall --client codex
  152. ```
  153. MCP server startup never installs or restores guidance. Run `konnect init`
  154. explicitly when you want those files installed; after `konnect uninstall`,
  155. starting the server leaves them removed.
  156. Guidance written by an older `konnect init` is not updated by upgrading the
  157. binary. `konnect status` compares every installed skill, agent, and hook with
  158. the bundle in the binary you run and marks each `current`, `different`, or
  159. `missing`. The server makes the same check once for each installed version:
  160. the first start after `konnect init` compares the files, records
  161. the result in `~/.konnect`, and adds a one-line notice to its `initialize`
  162. instructions if guidance is out of sync. Later starts reuse that record, so
  163. guidance you chose to keep is not reported again. `get_installation_info`
  164. shows the result. Re-run `konnect init` to update it.
  165. It overwrites differing files, so keep a copy of any file you edited. `--client` remains accepted in server
  166. commands for compatibility. For example, register a standalone binary with the
  167. Codex CLI using:
  168. ```bash
  169. codex mcp add konnect -- /path/to/konnect --client codex
  170. ```
  171. Claude remains the default when `--client` is omitted. The installer tracks the
  172. two clients independently, and a Codex install does not create or modify
  173. `~/.claude`.
  174. `--help` on any subcommand prints that subcommand's usage and writes nothing —
  175. `konnect init --help` describes the installer rather than running it. An
  176. argument Konnect does not recognise is an error rather than being ignored, so a
  177. typo such as `--cleint codex` stops instead of quietly installing for the
  178. default client.
  179. To verify which Konnect process an MCP client is actually using, call the
  180. always-visible `get_installation_info` tool. It reports the serving build,
  181. executable path, verified installation source when one can be proven, KiCad
  182. CLI and IPC detection, and restart guidance. A missing build commit or an
  183. `unknown` installation source means the available evidence was insufficient;
  184. it is not silently guessed from a directory name.
  185. ### macOS
  186. The [Releases](https://github.com/mixelpixx/Konnect/releases) page ships
  187. standalone server binaries for both Apple Silicon (`aarch64-apple-darwin`) and
  188. Intel (`x86_64-apple-darwin`). They are not yet code-signed, so if you download
  189. one through a browser, clear the quarantine flag before first launch:
  190. ```bash
  191. tar xzf konnect-v*-aarch64-apple-darwin.tar.gz
  192. xattr -d com.apple.quarantine ./konnect # only needed for browser downloads
  193. ./konnect --help
  194. ```
  195. Or build from source as above (verified on Apple Silicon; the same
  196. `target/release/konnect` binary is the MCP server).
  197. KiCad on macOS keeps its tools inside the app bundle and they are not on
  198. `PATH`, so point Konnect at them in `~/Library/Application Support/konnect/config.toml`:
  199. ```toml
  200. kicad_cli = "/Applications/KiCad/KiCad.app/Contents/MacOS/kicad-cli"
  201. kicad_binary = "/Applications/KiCad/KiCad.app/Contents/MacOS/kicad"
  202. # KiCad 10's IPC socket on macOS (enable it in KiCad:
  203. # Preferences → Plugins → "Enable KiCad API")
  204. ipc_address = "ipc:///tmp/kicad/api.sock"
  205. ```
  206. Claude Desktop's config lives at
  207. `~/Library/Application Support/Claude/claude_desktop_config.json`:
  208. ```json
  209. {
  210. "mcpServers": {
  211. "konnect": {
  212. "command": "/path/to/konnect"
  213. }
  214. }
  215. }
  216. ```
  217. For Claude Code, put the same snippet in a `.mcp.json` in your project root.
  218. The macOS PCM package (`konnect-pcm-v<version>-macos.zip`) bundles a universal
  219. server binary, so one download covers Apple Silicon and Intel. The schematic
  220. viewer compiles and launches on macOS (Tauri 2 uses the system WKWebView —
  221. WebView2 is only a Windows requirement) but hasn't had the same mileage as
  222. the Windows build yet.
  223. ## Setup with Claude Desktop
  224. After a PCM install, the server binary lives in your KiCAD documents folder:
  225. ```
  226. C:\Users\<YOU>\Documents\KiCad\10.0\3rdparty\plugins\com_github_mixelpixx_konnect\bin\konnect.exe
  227. ```
  228. Edit `%APPDATA%\Claude\claude_desktop_config.json`:
  229. ```json
  230. {
  231. "mcpServers": {
  232. "konnect": {
  233. "command": "C:\\Users\\<YOU>\\Documents\\KiCad\\10.0\\3rdparty\\plugins\\com_github_mixelpixx_konnect\\bin\\konnect.exe"
  234. }
  235. }
  236. }
  237. ```
  238. Restart Claude Desktop and the Konnect tools appear. For Claude Code, drop the same
  239. snippet into a `.mcp.json` in your project root (see [examples/](examples/)).
  240. ## Schematic viewer
  241. A standalone viewer that auto-refreshes as the schematic file changes:
  242. ```bash
  243. schematic-viewer.exe path\to\your\root_schematic.kicad_sch
  244. ```
  245. Point it at the root sheet of a hierarchical design and every sub-sheet is rendered
  246. too, with a depth-indented sheet selector in the toolbar. Edits saved from KiCAD (or
  247. made by the AI through the schematic tools) re-render only the sheets that changed
  248. and refresh the view live — rendering runs against temp-folder snapshots, so the
  249. viewer never blocks KiCAD from saving. Pan with click-drag, zoom with the wheel,
  250. `0` to fit, `R` to refresh, drag-and-drop to open a different file. Also launchable
  251. by the AI via the `open_schematic_viewer` tool.
  252. Needs the WebView2 runtime (pre-installed on Windows 10/11) and a KiCAD install for
  253. `kicad-cli` (auto-discovered, or pass `--kicad-cli <path>`). Built separately from
  254. the main workspace — see [DEV.md](DEV.md) for build steps.
  255. ## Requirements
  256. - KiCAD 10 (Windows is the most-tested platform; macOS works from the release
  257. binaries or a source build — see the [macOS section](#macos) above. Linux
  258. compiles and passes tests in CI but hasn't had per-platform QA yet; both are
  259. tracked on the [roadmap](ROADMAP.md))
  260. - `kicad-cli` (ships with KiCAD — used for exports, ERC, DRC)
  261. - For most PCB tools: KiCAD running with the target board open (IPC API).
  262. `place_component`, `move_component`, `rotate_component`, and (on KiCAD
  263. 10.0.6+) `flip_component` can safely fall back to a closed board file when
  264. IPC is unreachable. An older reachable KiCAD makes `flip_component` fail
  265. closed with `unsupported_capability`; it never edits the file underneath a
  266. live editor that cannot perform the native flip.
  267. ## License: free for the little guys
  268. Konnect is licensed under the **[GNU AGPL-3.0](LICENSE)**.
  269. If you're a hobbyist, student, freelancer, or open-source project: **use it freely,
  270. no strings attached.** Design boards, ship them, sell them.
  271. If you're a business: the AGPL requires that anything you build on or around Konnect —
  272. including software provided over a network — be open-sourced under the same license.
  273. If that doesn't work for you, **commercial licenses are available**: see
  274. [COMMERCIAL.md](COMMERCIAL.md).
  275. ## Relationship to KiCAD-MCP-Server
  276. The original [Python/TypeScript project](https://github.com/mixelpixx/KiCAD-MCP-Server)
  277. remains fully open (MIT) and maintained. Konnect is where new development happens —
  278. the architecture it proved, rebuilt for production:
  279. | | KiCAD-MCP-Server | Konnect |
  280. |---|---|---|
  281. | Runtime | Node.js + Python + SWIG bindings | Single static binary (20–25 MB) |
  282. | Tool call path | TS → subprocess → Python → SWIG C++ | Direct function call |
  283. | PCB backend | SWIG (deprecated by KiCAD) + experimental IPC | KiCAD 10 IPC API |
  284. | Schematic backend | kicad-skip + custom loaders | Native S-expression engine, atomic writes |
  285. | Context cost | Router pattern | Load/unload toolsets + observability |
  286. | Skills / agents | — | 6 skills + 2 agents bundled |
  287. | License | MIT | AGPL-3.0 + commercial |
  288. ## Troubleshooting
  289. **Plugin doesn't appear in KiCAD** — install via the Plugin and Content Manager (not
  290. manual copy), then restart KiCAD.
  291. **PCB tools return "KiCAD must be running with the board loaded"** — open KiCAD
  292. with that board first; most PCB tools talk to the running PCB editor. Only an
  293. unreachable KiCAD produces that message: if KiCAD is running and the tool
  294. refuses anyway, the error is the tool's own reason for refusing.
  295. `place_component`, `move_component`, `rotate_component`, and (on KiCAD
  296. 10.0.6+) `flip_component` can fall back to a closed board file when no KiCAD
  297. process is reachable. An older, reachable KiCAD makes `flip_component` refuse
  298. rather than silently editing the file underneath it.
  299. See [docs/TROUBLESHOOTING.md](docs/TROUBLESHOOTING.md) for socket setup, tools
  300. that don't appear after `load_toolset`, and transaction recovery.
  301. **"kicad-cli not found"** — common install paths are auto-detected; set the path
  302. explicitly in the plugin settings dialog, in a `settings.json` beside the binary,
  303. or in a `konnect.toml` in the working directory. (A file under any other name
  304. works only when passed with `--config`.)
  305. ## Support
  306. - Community Discord: [join the Konnect community](https://discord.gg/NVp9RGMmDu)
  307. for installation help, AI-client setup, design-workflow discussion,
  308. contributor coordination, and live project-status updates
  309. - Issues & feature requests: [GitHub Issues](https://github.com/mixelpixx/Konnect/issues)
  310. - Roadmap: [ROADMAP.md](ROADMAP.md)
  311. - Contributing: [CONTRIBUTING.md](CONTRIBUTING.md)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.