io.github.bunnyf/kicad-mcp-server
PYPI · KICAD-MCP-SERVER · SCANNED SEP 21
MCP server for AI-assisted PCB design with KiCad 9.x
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency31
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (GNU General Public License v3 or later (GPLv3+)) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 246 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 656 tokens (~28/item across 23 items; 23 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.bunnyf/kicad-mcp-server server?
io.github.bunnyf/kicad-mcp-server runs locally as a PyPI package, launched with uvx kicad-mcp-server. 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-server
claude mcp add bunnyf-kicad-mcp-server -- uvx kicad-mcp-server
{
"mcpServers": {
"bunnyf-kicad-mcp-server": {
"command": "uvx",
"args": [
"kicad-mcp-server"
]
}
}
} {
"servers": {
"bunnyf-kicad-mcp-server": {
"command": "uvx",
"args": [
"kicad-mcp-server"
]
}
}
} codex mcp add bunnyf-kicad-mcp-server -- uvx kicad-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bunnyf-kicad-mcp-server": {
"type": "local",
"command": [
"uvx",
"kicad-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add bunnyf-kicad-mcp-server --command uvx --arg kicad-mcp-server
mcp_servers:
bunnyf-kicad-mcp-server:
command: "uvx"
args: ["kicad-mcp-server"] {
"McpServers": {
"bunnyf-kicad-mcp-server": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"kicad-mcp-server"
]
}
}
} assistant mcp add bunnyf-kicad-mcp-server -t stdio -c uvx -a kicad-mcp-server
{
"mcpServers": {
"bunnyf-kicad-mcp-server": {
"command": "uvx",
"args": [
"kicad-mcp-server"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → 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 21 Sept 2026 · Analysed pypi/kicad-mcp-server@3.5.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
auto_route ~55
Auto-route PCB using FreeRouting (async by default, creates backup)
| Name | Type | Req | Description |
|---|---|---|---|
| async_mode | boolean | – | Run asynchronously (recommended) |
| max_passes | integer | – | Maximum routing passes |
| project | string | yes | Project name |
No output schema declared.
No examples provided.
cleanup_tasks ~33
Clean up old completed/failed tasks
| Name | Type | Req | Description |
|---|---|---|---|
| max_age_days | integer | – | Maximum age in days for tasks to keep |
No output schema declared.
No examples provided.
export_3d ~43
Export 3D rendered images (top, bottom, iso, all)
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
| view | string | – | View angle |
No output schema declared.
No examples provided.
export_all ~23
Export all available file types
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
export_bom ~25
Export Bill of Materials (CSV)
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
export_gerber ~26
Export Gerber and drill files
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
export_jlcpcb ~30
Export complete JLCPCB/PCBWay manufacturing package
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
export_netlist ~46
Export netlist (kicadxml, spice, cadstar, orcadpcb2)
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format |
| project | string | yes | Project name |
No output schema declared.
No examples provided.
export_pdf ~41
Export PCB as PDF
| Name | Type | Req | Description |
|---|---|---|---|
| layers | string | – | Layer set (top, bottom, all) or custom layers |
| project | string | yes | Project name |
No output schema declared.
No examples provided.
export_sch_pdf ~24
Export schematic as PDF
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
export_sch_svg ~24
Export schematic as SVG
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
export_step ~26
Export PCB as STEP 3D model
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
export_svg ~36
Export PCB as SVG images
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
| view | string | – | View (top/bottom/all) |
No output schema declared.
No examples provided.
fill_zones ~25
Fill all copper zones in PCB
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
get_board_info ~29
Get PCB board information (dimensions, layers, components)
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
get_output_files ~23
List project output files
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
get_task_status ~26
Get status of an async task
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | Task ID |
No output schema declared.
No examples provided.
get_version ~12
Get version information
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_projects ~12
List all projects
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tasks ~13
List all async tasks
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_file ~27
Read file content (restricted to project/task directories)
| Name | Type | Req | Description |
|---|---|---|---|
| filepath | string | yes | File path |
No output schema declared.
No examples provided.
run_drc ~29
Run Design Rule Check (DRC) on PCB
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
run_erc ~28
Run Electrical Rule Check (ERC) on schematic
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
What is the io.github.bunnyf/kicad-mcp-server server?
io.github.bunnyf/kicad-mcp-server is listed in the public MCP registry as io.github.bunnyf/kicad-mcp-server. MCP server for AI-assisted PCB design with KiCad 9.x. This page covers its PyPI package (kicad-mcp-server).
Is the io.github.bunnyf/kicad-mcp-server server safe to use?
io.github.bunnyf/kicad-mcp-server scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 io.github.bunnyf/kicad-mcp-server server expose?
io.github.bunnyf/kicad-mcp-server exposes 23 tools: list_projects, run_drc, run_erc, fill_zones, auto_route, and 18 more. Their descriptions and schemas cost roughly 656 tokens of context every time the server is loaded.
Is the io.github.bunnyf/kicad-mcp-server server still maintained?
io.github.bunnyf/kicad-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.