by oaslananka
Production-grade MCP server for KiCad 10/9 — AI-driven schematic capture, PCB layout, DRC/ERC/DFM validation, signal & power integrity, EMC checks, SPICE simulation, FreeRouting, and gated manufacturing exports (Gerber, BOM, IPC-2581, STEP).
# Add to your Claude Code skills
git clone https://github.com/oaslananka/kicad-mcp-proKiCad MCP Pro is a production-focused Model Context Protocol server for KiCad PCB and schematic workflows. It gives agents project setup, schematic editing, PCB inspection and edits, validation gates, DFM checks, SI/PI helpers, simulation helpers, and release-gated manufacturing export.
Use it with Claude Desktop, Claude Code, Cursor, VS Code, Codex, or any MCP-compatible client.
Install and run with uvx:
uvx kicad-mcp-pro --help
uvx kicad-mcp-pro health --json
uvx kicad-mcp-pro doctor --json
uvx kicad-mcp-pro serve
Or install with pip:
pip install kicad-mcp-pro
kicad-mcp-pro --help
kicad-mcp-pro health --json
kicad-mcp-pro serve
The default no-subcommand invocation still starts the stdio MCP server for backward compatibility. is safe to run when KiCad is not running; it reports KiCad IPC as deferred instead of crashing. adds deeper CLI and IPC diagnostics for launchers such as .
No comments yet. Be the first to share your thoughts!
health --jsondoctor --jsonkicad-studioUse an absolute KiCad project path:
{
"servers": {
"kicad": {
"type": "stdio",
"command": "uvx",
"args": ["kicad-mcp-pro"],
"env": {
"KICAD_MCP_PROJECT_DIR": "/absolute/path/to/your/kicad-project",
"KICAD_MCP_WORKSPACE_ROOT": "/absolute/path/to/your/workspace",
"KICAD_MCP_PROFILE": "pcb_only"
}
}
}
}
More client examples:
export_manufacturing_package().minimal, pcb_only, schematic_only, manufacturing, analysis, and agent_full.kicad_set_project()
project_get_design_spec()
sch_build_circuit()
pcb_sync_from_schematic()
project_quality_gate_report()
export_manufacturing_package()
Demo media guidance lives in docs/demo-media.md.
Normal CI and security workflows run on pull requests, pushes, and merge queue events. Release, publish, mirroring, deployment, and token-backed jobs remain guarded behind explicit repository checks and protected environments.
The project uses Dependabot, Renovate, CodeQL, Gitleaks, Trivy, OpenSSF Scorecard, Codecov, release-please, SBOM generation, Sigstore signing, and GitHub artifact attestations for release hardening.
Operational references: