Autoroute a KiCad board and validate the result through MCP
Run a bounded Freerouting pass on a KiCad board, inspect DRC and unrouted nets, then prepare fabrication exports only after the result is reviewed.
npx skills add agentskillexchange/skills --skill autoroute-kicad-board-and-validate-result-through-mcp
Invoke this workflow when an electronics agent needs to route an existing KiCad board and return a checked revision with fabrication artifacts. Supply the project path, a working copy or checkpoint, allowed routing scope, routing limits, and the desired export directory. The boundary is a controlled board-routing pass followed by design-rule verification and a review handoff.
What this skill actually does
Install KiCad with its pcbnew Python bindings, Node.js, the server’s Python dependencies, and Freerouting. Clone the upstream v2.9.0 release, install its Node dependencies, install requirements.txt with the Python interpreter that can import pcbnew, and run npm run build. Configure the MCP client to start node /absolute/path/KiCAD-MCP-Server/dist/index.js with the documented KiCad Python paths. Freerouting requires its JAR and a supported Java runtime or the documented container alternative. Use the platform installation guide to verify these prerequisites.
Open the selected board and inspect project state and nets before changing it. Save a named checkpoint with snapshot_project. Discover the autorouting tools through search_tools and inspect their current schemas. Follow the upstream recipe: verify Freerouting dependencies, run autoroute with a bounded timeout and pass limit, then call run_drc and inspect get_drc_violations. Compare unresolved connections and violations with the baseline. Report routing or import failures explicitly and inspect the resulting board before accepting the saved revision.
Save the approved result with the board lifecycle tools and prepare export_gerber and export_drill outputs only when the requested checks permit fabrication handoff. Return the board path, routing limits, DRC findings, remaining unrouted nets, and actual generated files; unresolved errors remain visible. Ordering boards is outside this workflow. The server’s readonly and manufacturing operating modes exclude editing operations, so the routing session requires a configuration that offers routing tools. MCP is central to invocation. Reviewed v2.9.0 documentation supports this sequence. No KiCad installation, electrical validation, or runtime security test was performed during intake.