kicad-chatgpt-mcp (faizannazir) errors

3 recurring problems engineers report in kicad-chatgpt-mcp (faizannazir), ranked by impact.

#177 by errors trackedECAD

Recurring kicad-chatgpt-mcp (faizannazir) errors, by impact

  1. 1A KiCad MCP evaluation found the server inventing connectivity from pin proximity and reporting DRC passes when checks never ran.ECAD · Agent failure · 1 report74
  2. 2A KiCad MCP server added a check that runs KiCad's ERC and DRC together, refuses if the board asked about is not the one loaded, and ties the result to SHA-256 hashes of the saved schematic and PCB, failing if either changes during the check. The author says it does not replace KiCad's checks or sign off fab, SI, thermal or EMC. People building agents for ECAD are now writing their own 'was this check run on the right revision' layer.ECAD · Agent failure · 1 report66
  3. 3A KiCad MCP server got pins, ERC and board sync wrong in quiet ways. Pin coordinates ignored mirroring. Parsed schematics went stale after save. ERC results got dropped when KiCad exited non-zero for violations. Schematic-to-PCB sync reloaded the board from disk and lost unsaved outline geometry. Gerber export now checks layer identity by filename. The new manufacturing manifest explicitly does not claim fabrication readiness.ECAD · Agent failure · 1 report66

How it fails

  1. Agent failure3

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.