Konnect Lets Claude Edit KiCad 10 Boards, and Writes Schematic Files Itself Because the API Cannot

Konnect, an open-source plugin that lets Claude or another MCP client design circuits in KiCad 10, edits schematics by writing .kicad_sch files directly. The reason is in KiCad's own documentation: the IPC API that plugins use has no schematic support in KiCad 9 or 10.

That one design choice separates the two halves of the tool, and it is where a hardware designer should read the README most carefully. The repository belongs to a user named mixelpixx, who is the only contributor the page lists. It shows 1,168 commits, 138 forks and 49 open pull requests.

What the 228 tools do

MCP, the Model Context Protocol, is the standard that lets a language model call named tools in another program. Konnect packages that for KiCad as a single Rust binary of 20 to 25 MB.

The README lists schematic placement and wiring by pin name, footprint placement and routing, electrical and design rule checks, and exports to Gerber, drill, BOM, pick-and-place, 3D and PDF. It also searches a local catalogue of 2.5 million JLCPCB parts and carries reference circuits for USB-C, an LDO regulator, a buck converter, an STM32 and an I2C bus.

The count is not settled. The README says 228 tools across 21 toolsets, and the About section says 217. Exposing all of them to a model costs roughly 23K tokens a listing, so Konnect ships a router that loads toolsets on demand.

Where KiCad's API stops

KiCad's IPC API documentation is blunt about scope. It says the API in KiCad 9 and 10 "only supports communication with a running instance of the KiCad GUI", that plugins are limited to the PCB Editor, and that it "has no support for plotting or exporting files from KiCad designs". Schematic Editor plugins, plotting and export arrive in KiCad 11.

Konnect works around each gap with a different mechanism.

Job	KiCad 10 IPC API	What Konnect does
PCB edits	Supported, GUI must be running	Uses the IPC API (NNG and protobuf)
Schematic edits	Not supported	Writes .kicad_sch files, atomic writes
Plot and export	Not supported	Calls kicad-cli for exports, ERC and DRC
Autorouting	Not covered by the docs read	Freerouting, optional Specctra bridge off by default

The file-edit path is the risk

Schematic edits that go to disk do not go through the running editor at all, and the README says they do not require KiCad to be open. It adds a related caveat for boards: when the IPC connection is unreachable, some placement tools edit the closed board file directly, and older KiCad versions refuse flip_component rather than touching a file under a running editor.

Two other limits are described plainly. The project is in beta, and the README says output should be reviewed by a person before fabrication. The Specctra profile keeps only fixed straight tracks and through vias, and rejects arcs, zones and unlocked routing before changing anything.

The reference circuits suggest the intended first job: a USB-C power input feeding a regulator for an STM32 board. A passing design rule check says the geometry is legal, not that the circuit is right, which is why the README leaves the review to a person.

What the star count says

The repository shows 1.2k stars, a rounded figure. As the Terminal wrote about REA's 270,097 stars, stars measure attention. Konnect's 174 open issues are a better gauge of who is actually running it.

Agent workflows differ in how many checkpoints they put between a model and its output; AWS's AI-DLC workflow is the Terminal's earlier example, with 33 stages. The Konnect README describes no checkpoint between the model and the file.

Other practical limits: Windows is the most-tested platform, Linux builds and passes CI but has no per-platform QA, and macOS binaries are not code-signed. konnect init overwrites differing skill, agent and hook files, so back up edits first.

KiCad 11 is the version to watch. Its schematic and export APIs would remove the reason Konnect writes files itself, and the README says its native Specctra bridge is not the KiCad 11 integration path.

The licence is AGPL-3.0. Hobbyists, students and open-source projects can use it freely; businesses must open-source anything built on or around it or buy a commercial licence described in COMMERCIAL.md.