by oaslananka
MCP server for KiCad, connecting AI agents to schematic and PCB workflows, ERC/DRC validation, DFM checks, BOM analysis, and manufacturing preparation—with controlled edits and human-gated release workflows.
# Add to your Claude Code skills
git clone https://github.com/oaslananka/kicad-mcp-proGuides for using ai agents skills like kicad-mcp-pro.
Last scanned: 5/30/2026
{
"issues": [
{
"type": "clone-failed",
"message": "Could not clone repository",
"severity": "medium"
}
],
"status": "WARNING",
"scannedAt": "2026-05-30T16:30:47.666Z",
"npmAuditRan": false,
"pipAuditRan": false
}See how kicad-mcp-pro compares with popular alternatives.
kicad-mcp-pro is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by oaslananka. MCP server for KiCad, connecting AI agents to schematic and PCB workflows, ERC/DRC validation, DFM checks, BOM analysis, and manufacturing preparation—with controlled edits and human-gated release workflows. It has 158 GitHub stars.
kicad-mcp-pro returned warnings in SkillsLLM's automated security scan. It has no critical vulnerabilities, but review the flagged issues in the Security Report section before adding it to your workflow.
Clone the repository with "git clone https://github.com/oaslananka/kicad-mcp-pro" and add it to your Claude Code skills directory (see the Installation section above).
kicad-mcp-pro is primarily written in Python. It is open-source under oaslananka on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh kicad-mcp-pro against similar tools.
No comments yet. Be the first to share your thoughts!
Requires a passing catalog security scan.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
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, release with manufacturing mode for human-gated handoff, or expert/full only for advanced trusted clients. Current catalog counts and context-size estimates come from docs/evidence/progressive-disclosure-profile-snapshot.json; see docs/agents/progressive-disclosure.md.
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.
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.
| Field | Value |
|---|---|
| Canonical repository | oaslananka/kicad-mcp-pro |
| PyPI package | kicad-mcp-pro |
| npm wrapper | kicad-mcp-pro |
| MCP Registry name | io.github.oaslananka/kicad-mcp-pro |
| Version | 4.4.0 |
| OSS maturity report | docs/repo-maturity-report.md |
| OpenSSF evidence | docs/openssf-evidence.md |
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.
uvx kicad-mcp-pro init
uvx kicad-mcp-pro tray
uvx kicad-mcp-pro dashboard --open
uvx kicad-mcp-pro --transport streamable-http --port 3334
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.
uvx kicad-mcp-pro dashboard --host 127.0.0.1 --port 3334 --open
# http://127.0.0.1:3334/ui
The documentation is organized from setup to operation:
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.
The published documentation site is available at https://oaslananka.github.io/kicad-mcp-pro/.
KiCad MCP Pro supports stdio and Streamable HTTP. Streamable HTTP is served at
/mcp by default and can be moved with KICAD_MCP_MOUNT_PATH.
uvx kicad-mcp-pro --transport streamable-http --host 127.0.0.1 --port 3334
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.
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.
The canonical metadata inputs are pyproject.toml for package version and repository identity, and compatibility.yaml for KiCad and MCP supp