KiCad MCP Pro
PYPI · KICAD-MCP-PRO · 3 COMPONENTS
Production-grade MCP server for KiCad EDA—PCB design, DRC, simulation, BOM, DFM, and manufacturing.
Available components
Last scanned (1 day ago)
Scores higher than 78% of PyPI servers
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 6 of 73 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to oaslananka/kicad-mcp-pro). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1750 tokens (~38/item across 45 items; 24 tools + 21 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Package version: 4.6.1 → 4.7.0 functional
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 0
- Package version: 4.5.0 → 4.6.1 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 4.4.0 → 4.5.0 functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 24 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 4.3.0 → 4.4.0 functional
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/kicad-mcp-pro@4.7.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | oaslananka/kicad-mcp-pro |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/oaslananka/kicad-mcp-pro/.github/workflows/publish-python.yml@refs/tags/mcp-server-v4.7.0 |
| Rekor log index | 3683838587 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:29071c5156583f96c131a83db58fb92b8ba40545e838da8a54c6c105a74db159 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 73 packages
| Packages resolved | 73 |
|---|---|
| Stale | 5 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dfm_run_manufacturer_check ~25
Run a manufacturer-aware DFM review using the active bundled profile.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | array | – | – |
| failure_mode | string | – | – |
| findings | array | – | – |
| metadata | object | – | – |
| next_action | string | – | – |
| remediation | string | – | – |
| retryable | boolean | – | – |
| schema_version | string | – | – |
| severity | string | – | – |
| summary | string | – | – |
| text | string | – | – |
| verdict | string | – | – |
No examples provided.
kicad_get_project_info ~37
Show the currently configured KiCad project paths. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
kicad_get_server_info ~39
Return versioned server information and capability diagnostics for clients. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
kicad_get_tools_in_category ~39
Get tool names in a category, optionally filtered by maturity.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| maturity | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
kicad_get_version ~37
Get KiCad version information and current connection status. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
kicad_list_tool_categories ~36
List all available tool categories and capabilities. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
kicad_set_project ~70
Set the active KiCad project directory and file paths. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
| Name | Type | Req | Description |
|---|---|---|---|
| output_dir | string | – | – |
| pcb_file | string | – | – |
| project_dir | string | yes | – |
| sch_file | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
lib_get_bom_with_pricing ~38
Generate a live BOM summary with unit and extended pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| quantity | integer | – | – |
| source | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
lib_verify_component_contract ~161
Verify a placed component's symbol, footprint, and pins actually match. For the given schematic reference designator this checks, entirely from local project files (no network access): - symbol pin count vs footprint connectable pad count - pin numbers vs pad numbers - footprint courtyard / fabrication / silkscreen completeness - 3D model presence (advisory) - datasheet evidence (advisory; never auto-filled) Returns a JSON object with a ``status`` of PASS / WARN / FAIL and a list of per-check ``findings``. FAIL marks a structural contract violation, WARN marks a quality/completeness smell, and INFO is advisory evidence that never changes the overall status.
| Name | Type | Req | Description |
|---|---|---|---|
| reference | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pcb_get_board_summary ~33
Summarize the current board. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | array | – | – |
| failure_mode | string | – | – |
| findings | array | – | – |
| metadata | object | – | – |
| next_action | string | – | – |
| remediation | string | – | – |
| retryable | boolean | – | – |
| schema_version | string | – | – |
| severity | string | – | – |
| summary | string | – | – |
| text | string | – | – |
| verdict | string | – | – |
No examples provided.
pcb_get_design_rules ~36
Read the active board design rules file when available. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pcb_get_stackup ~32
Show the current stackup. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
pcb_visual_qa ~133
Headless PCB readability QA: off-board parts, silk and body overlap. A fast, file-backed first pass that runs without a live KiCad: it flags footprints whose body leaves the board outline, reference designators that collide on the silkscreen, and overlapping footprint bodies — directly from the ``.kicad_pcb`` geometry. It complements (does not replace) the authoritative DRC run, which remains the sign-off check for courtyard and silk clipping. Returns JSON with an overall PASS/INFO/WARN status and per-finding refs/positions.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
project_design_workflow ~131
Return the professional PCB design workflow as a typed phase state machine. Lays out the canonical Planner -> Builder -> Verifier -> Fixer -> Release sequence, with the high-level tool and the quality gates each phase must pass. Pass the phases already finished in ``completed_phases``; the tool marks them COMPLETE, reports the first remaining phase as READY (the current step) with its next action and gates, and flags when a human gate is required. Read-only and headless — use it to drive an autonomous design run step by step.
| Name | Type | Req | Description |
|---|---|---|---|
| completed_phases | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
project_get_next_action ~24
Return the next high-priority action derived from the current project gate.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | – | – |
| gate | string | – | – |
| next_action | string | – | – |
| reason | string | – | – |
| status | string | yes | – |
| suggested_tool | string | – | – |
| text | string | yes | – |
| verdict | string | – | – |
No examples provided.
project_quality_gate ~41
Run the full project quality gate across schematic, PCB, DFM, and parity checks.
| Name | Type | Req | Description |
|---|---|---|---|
| manufacturer | string | – | – |
| tier | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | array | – | – |
| failure_mode | string | – | – |
| findings | array | – | – |
| metadata | object | – | – |
| next_action | string | – | – |
| remediation | string | – | – |
| retryable | boolean | – | – |
| schema_version | string | – | – |
| severity | string | – | – |
| summary | string | – | – |
| text | string | – | – |
| verdict | string | – | – |
No examples provided.
run_drc ~34
Return full DRC report with PCB violations, unconnected items, and courtyard issues.
| Name | Type | Req | Description |
|---|---|---|---|
| save_report | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | array | – | – |
| failure_mode | string | – | – |
| findings | array | – | – |
| metadata | object | – | – |
| next_action | string | – | – |
| remediation | string | – | – |
| retryable | boolean | – | – |
| schema_version | string | – | – |
| severity | string | – | – |
| summary | string | – | – |
| text | string | – | – |
| verdict | string | – | – |
No examples provided.
run_erc ~39
Run schematic electrical rule checks. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
| Name | Type | Req | Description |
|---|---|---|---|
| save_report | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | array | – | – |
| failure_mode | string | – | – |
| findings | array | – | – |
| metadata | object | – | – |
| next_action | string | – | – |
| remediation | string | – | – |
| retryable | boolean | – | – |
| schema_version | string | – | – |
| severity | string | – | – |
| summary | string | – | – |
| text | string | – | – |
| verdict | string | – | – |
No examples provided.
sch_get_bounding_boxes ~124
Return the estimated bounding box of every symbol in the active schematic. Use this before calling sch_add_symbol or sch_build_circuit to understand which areas of the schematic sheet are already occupied. The bounding boxes are heuristic estimates (KiCad does not expose exact extents via the file API) but are conservative enough to avoid overlap in practice. Returns: A table of all symbols with their centre position and estimated bounding-box corners (x_min, y_min, x_max, y_max) in mm, plus an occupied-area summary.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sch_get_connectivity_graph ~24
Summarize the active schematic as a textual net connectivity graph.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sch_get_symbols ~47
List all schematic symbols, optionally from a child sheet. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
| Name | Type | Req | Description |
|---|---|---|---|
| sheet | – | – | – |
| sheet_file | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sch_visual_qa ~94
Run headless visual/readability QA on the active schematic sheet(s). Detects readability defects ERC cannot — overlapping labels, off-sheet symbols or labels, dense unreadable label fanout, and title-block gaps — directly from the schematic S-expression geometry, with no rendering required. Returns JSON with an overall PASS/WARN/FAIL status and per-sheet findings carrying object refs and positions for follow-up.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
validate_design ~33
Run DRC and ERC and summarize readiness. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
validate_footprints_vs_schematic ~39
Compare PCB footprint references against the schematic symbol references. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the KiCad MCP Pro server?
KiCad MCP Pro runs locally as a PyPI package, launched with uvx kicad-mcp-pro. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · kicad-mcp-pro
claude mcp add oaslananka-kicad-mcp-pro -- uvx kicad-mcp-pro
What is the KiCad MCP Pro server?
KiCad MCP Pro is listed in the public MCP registry as io.github.oaslananka/kicad-mcp-pro. Production-grade MCP server for KiCad EDA, PCB design, DRC, simulation, BOM, DFM, and manufacturing. This page covers its PyPI package (kicad-mcp-pro).
Is the KiCad MCP Pro server safe to use?
KiCad MCP Pro scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the KiCad MCP Pro server expose?
KiCad MCP Pro exposes 24 tools: kicad_list_tool_categories, kicad_get_tools_in_category, kicad_set_project, kicad_get_project_info, project_design_workflow, and 19 more. Their descriptions and schemas cost roughly 1,346 tokens of context every time the server is loaded.
Is the KiCad MCP Pro server still maintained?
KiCad MCP Pro is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the KiCad MCP Pro server under?
KiCad MCP Pro declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.