KiCad MCP Pro is a Model Context Protocol server for KiCad EDA workflows. It exposes tools, resources, and prompts for schematic, PCB, validation, DFM, and manufacturing export automation.
The server now starts with the bounded default profile: 24 read-only review tools instead of the complete expert catalog. Use build with write mode for controlled edits, with manufacturing mode for human-gated handoff, or / only for advanced trusted clients. Current catalog counts and context-size estimates come from ; see .
Node.js launcher for kicad-mcp-pro (Python MCP server for KiCad EDA).
Telemetry and error reporting are disabled by default. Opt-in OpenTelemetry
configuration is documented in
docs/configuration.md, and privacy rules
are documented in docs/privacy.md.
Scope and honesty
KiCad MCP Pro is a professional first-pass design and review assistant, not an
automated sign-off authority. ERC/DRC and the export pipeline drive KiCad's own
engines. The signal-integrity, power-integrity, EMC, and thermal tools are
first-order, closed-form estimates (typically ~5–10% accuracy) — fast first-pass
review, not a substitute for a 2D/3D field solver, EM/FEA simulation, or formal
sign-off. Live component sourcing uses the JLCPCB public catalog by default; Nexar,
DigiKey, and Mouser are available only when their API credentials are configured. What
fraction of KiCad's programmatic surface the server drives is tracked openly in the
capability-parity matrix. Raw tool count and
capability coverage are inventory metrics, not the headline product-quality measure. End-to-end
task outcome, mutation recovery, corruption, required DRC execution, and manufacturing
reproducibility are the outcome KPIs. The committed
native-live example evidence
intentionally reports insufficient_evidence; representative-corpus target attainment remains
separate until the qualification work in #730 is complete.
Download the latest installer from the
GitHub releases page.
The Tauri desktop app starts the Python dashboard server automatically and opens
the GUI at http://127.0.0.1:3334/ui. Desktop releases launch the matching exact
backend version and verify its desktop compatibility handshake before use; see
Installation.
The existing KiCad PCM Companion is being upgraded to a KiCad 10 IPC toolbar
plugin in packages/kicad-plugin/. It reads the active
PCB and links to the existing local dashboard. The IPC upgrade is read-only;
live desktop acceptance and release are pending.
The kicad_capability_parity() tool reports, per workflow domain, what fraction of
KiCad's programmatically reachable surface this server can drive (currently 76.6%),
keeping genuine gaps distinct from gui-only-no-api items that KiCad exposes no
headless API for.
Streamable HTTP clients must send Accept: application/json, text/event-stream and
Content-Type: application/json. The primary public MCP contract is
2026-07-28: modern clients send MCP-Protocol-Version: 2026-07-28, the
method/name transport headers required by the final protocol, and the per-request
client metadata envelope.
Backward-compatible 2025-11-25 clients remain supported through the SDK's
legacy initialize negotiation. Those clients echo the negotiated protocol
version on follow-up requests and, when KICAD_MCP_STATEFUL_HTTP=1, also echo
MCP-Session-Id. Final 2026-07-28 traffic is stateless and does not create MCP
sessions.
The deprecated HTTP+SSE fallback routes are disabled by default. Set
KICAD_MCP_LEGACY_SSE=1 only for older clients that cannot use Streamable HTTP.
Install
Published packages:
uvx kicad-mcp-pro --help
npx kicad-mcp-pro --help
Fresh source checkout on supported Linux hosts:
./scripts/bootstrap-dev.sh
source .dev-env.sh
pnpm run dev:doctor -- --ci
The repository bootstrap installs checksum-pinned Python, uv/uvx, Node.js,
pnpm, Task, and Rust tooling into ignored checkout-local roots and performs
frozen dependency installation. It does not modify global tool directories.
See the reproducible bootstrap guide
for --core-only, --check, cleanup, upgrade, and KiCad capability modes.
Package metadata
The canonical metadata inputs are pyproject.toml for package version and repository identity, and compatibility.yaml for KiCad and MCP support policy. server.json is the generated registry manifest. pnpm run metadata:sync renders the public surfaces, and pnpm run metadata:check verifies them in CI and release validation.
This repository owns the product-level agent plugin and KiCad-specific skills for
KiCad MCP Pro. The central agent-tools
repository should catalog this plugin, but the manifest and workflow instructions live
here so they stay synchronized with the actual MCP server tools.
Schematic inspection, ERC, connectivity, power, symbol, and readability workflow.
Agent setup
KiCad MCP Pro can be launched with the published Python package, npm wrapper, or the
container metadata declared in server.json. Common local starts are:
KiCad MCP Pro is an engineering assistant, not an autonomous manufacturing sign-off
authority. Generated PCB and fabrication outputs require qualified human review before
fabrication or assembly.
Development
New contributors should start with ARCHITECTURE.md, which maps
the five layers (transport → MCP protocol → orchestration → KiCad adapter seam →
pure domain) and shows exactly how to add a new tool. The runtime model and
quality-gate stack are documented in
docs/development/architecture.md.
The project uses a Taskfile.yml for common development commands. After
cloning the repository:
task install # Install all dependencies (pnpm + uv)
task verify # Run the local quality gate: lint → format → typecheck → test → build
task test # Run unit tests only
task lint # Run lint and metadata checks
task format # Auto-format the codebase
task typecheck # Run strict static type checking
task build # Build release artifacts
task ci # Run the local equivalent of the full CI pipeline
task hooks # Install repository-pinned Lefthook git hooks
All changes must pass task verify before opening a pull request.
Contributing
Read CONTRIBUTING.md before opening a pull request. All
changes must pass the repository's format, lint, type-check, test, workflow,
security, and package metadata gates.
Independent industry coverage
JLCPCB (October 14, 2026) — KiCad MCP: How to Design a PCB with Claude Code documents a hands-on KiCad MCP Pro workflow for an XL4015/LM358 buck-converter design, including checks and limitations. The board was not fabricated or bench-tested. This is independent coverage, not a JLCPCB endorsement or partnership; reported issues are being evaluated in #1314.
Cite this software
If you use KiCad MCP Pro in research or a technical publication, cite the
archived release via its DOI (see CITATION.cff for full
metadata):
@software{aslan_kicad_mcp_pro,
author = {Aslan, Osman},
title = {KiCad MCP Pro},
license = {MIT},
url = {https://github.com/oaslananka/kicad-mcp-pro},
doi = {10.5281/zenodo.21283791}
}
Every GitHub release is archived on Zenodo under this concept DOI, which
always resolves to the most recent version.