Konnect MCP server (KiCad) errors
4 recurring problems engineers report in Konnect MCP server (KiCad), ranked by impact.
#143 by errors trackedECAD
Recurring Konnect MCP server (KiCad) errors, by impact
- 1Flipping a component with Konnect does not mirror inner copper layers the way KiCad does. On an 8-layer board the footprint moved sides but its pads stayed on In5.Cu instead of mirroring to In2.Cu, and 5 net-ties ended up tying LPDDR4 branch nets on the In5 GND plane layer instead of In2, with no warning.ECAD · Agent failure · 1 report 186
- 2Moving a component onto another net's via through Konnect's IPC move silently re-nets the copper: KiCad changes the via's net to the moved pad's net. A ground stitching via took on the test point's supply net and the ground plane lost it, while DRC stayed clean. A synthetic repro with KiCad's own Python shows a closed-file move does not re-net, so the hazard is specific to the agent's live move path.ECAD · Agent failure · 1 report 177
- 3The connect_to_net and connect_pins tools resolve a reference plus pin number by taking the first placed symbol with the pin, picked by file order. With two Device:R symbols both referenced R4, the call wired one of them and answered isError: false; the netlist showed the second R4's pin as unconnected, and nothing in the response said the second R4 exists.ECAD · Agent failure · 1 report 170
- 4On any board with a copper zone, update_pcb_from_schematic marked every board net as routed and refused every pad-net change as routed_pad_net_change, even when neither the old nor the new net had any track, arc or via. The zone's own net is readable in the protobuf, but the tool failed closed on all nets instead of just the zone's. Since nearly every real board has a ground pour, no connection on such a board could be changed by the agent.ECAD · Agent failure · 1 report 163
How it fails
Engineering tools that address these errors
Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.