Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.daedalus/mcp-kicad

PYPI · MCP-KICAD · SCANNED SEP 20

MCP server exposing KiCad PCB Editor functionality via IPC API

Available components

−15 this week 64 Trust /100
Trust breakdown (7 categories)

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 native-build step with no shell scripting around it. View diagnostics → Pass
  • 2 of 27 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability76
  • 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 2216 tokens (~50/item across 44 items; 41 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 9% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_item" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 42 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
Install

How do I install the io.github.daedalus/mcp-kicad server?

io.github.daedalus/mcp-kicad runs locally as a PyPI package, launched with uvx mcp-kicad. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-kicad

# add to Claude Code
claude mcp add daedalus-mcp-kicad -- uvx mcp-kicad
// .cursor/mcp.json
{
  "mcpServers": {
    "daedalus-mcp-kicad": {
      "command": "uvx",
      "args": [
        "mcp-kicad"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "daedalus-mcp-kicad": {
      "command": "uvx",
      "args": [
        "mcp-kicad"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add daedalus-mcp-kicad -- uvx mcp-kicad
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "daedalus-mcp-kicad": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-kicad"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add daedalus-mcp-kicad --command uvx --arg mcp-kicad
# ~/.hermes/config.yaml
mcp_servers:
  daedalus-mcp-kicad:
    command: "uvx"
    args: ["mcp-kicad"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "daedalus-mcp-kicad": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-kicad"
      ]
    }
  }
}
# add to Vellum
assistant mcp add daedalus-mcp-kicad -t stdio -c uvx -a mcp-kicad
// mcp.json
{
  "mcpServers": {
    "daedalus-mcp-kicad": {
      "command": "uvx",
      "args": [
        "mcp-kicad"
      ]
    }
  }
}
Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 −18
    • Malware scan: pass → unverified security
    • Stability: pass → 0.80 functional
  • 17 Sept 26 +15
    • Malware scan: unverified → pass security
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 −14
    • Malware scan: pass → unverified security
  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 10 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 20 Sept 2026 · Analysed pypi/mcp-kicad@0.1.1

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 hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 27 packages
Packages resolved 27
Stale 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 41 exposed · ~2,179 tokens

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 →

Tool Tokens
add_to_selection ~24

Add an item to the selection.

NameTypeReqDescription
item_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

check_connection ~69

Check if currently connected to KiCad. Returns connection status, KiCad version, and whether versions match. Returns: Dictionary with connection status and version info. Example: >>> check_connection() {"connected": True, "version": "9.0.1", "version_match": True}

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

clear_selection ~13

Clear the current selection.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

connect_kicad ~108

Connect to a running KiCad instance via the IPC API. This must be called before any other operations. Ensure KiCad is running with the API server enabled in Preferences > Plugins.

NameTypeReqDescription
kicad_tokenOptional API token for authentication.
socket_pathOptional path to IPC socket. If not provided, reads from KICAD_API_SOCKET environment variable or uses default platform path.
timeout_msintegerConnection timeout in milliseconds. Default 2000.

Structured output declared, but exposes no named fields.

No examples provided.

create_arc ~78

Create an arc on the board.

NameTypeReqDescription
center_xnumberyes
center_ynumberyes
end_xnumberyes
end_ynumberyes
layerstring
line_widthnumber
start_xnumberyes
start_ynumberyes

Structured output declared, but exposes no named fields.

No examples provided.

create_circle ~58

Create a circle on the board.

NameTypeReqDescription
filledboolean
layerstring
line_widthnumber
radiusnumberyes
xnumberyes
ynumberyes

Structured output declared, but exposes no named fields.

No examples provided.

create_footprint ~66

Place a footprint on the board.

NameTypeReqDescription
footprintstringyes
layerstring
referencestringyes
rotationnumber
valuestringyes
xnumberyes
ynumberyes

Structured output declared, but exposes no named fields.

No examples provided.

create_line ~63

Create a line segment on the board.

NameTypeReqDescription
end_xnumberyes
end_ynumberyes
layerstring
line_widthnumber
start_xnumberyes
start_ynumberyes

Structured output declared, but exposes no named fields.

No examples provided.

create_net ~31

Create a new net on the board.

NameTypeReqDescription
namestringyes
netclassstring

Structured output declared, but exposes no named fields.

No examples provided.

create_rectangle ~72

Create a rectangle on the board.

NameTypeReqDescription
filledboolean
heightnumberyes
layerstring
line_widthnumber
rotationnumber
widthnumberyes
xnumberyes
ynumberyes

Structured output declared, but exposes no named fields.

No examples provided.

create_text ~65

Create a text element on the board.

NameTypeReqDescription
layerstring
rotationnumber
sizenumber
textstringyes
thicknessnumber
xnumberyes
ynumberyes

Structured output declared, but exposes no named fields.

No examples provided.

create_track ~69

Create a track segment on the board.

NameTypeReqDescription
end_xnumberyes
end_ynumberyes
layerstring
netstring
start_xnumberyes
start_ynumberyes
widthnumber

Structured output declared, but exposes no named fields.

No examples provided.

create_via ~58

Create a via on the board.

NameTypeReqDescription
diameternumber
drillnumber
layersarray
netstring
xnumberyes
ynumberyes

Structured output declared, but exposes no named fields.

No examples provided.

create_zone ~43

Create a copper zone on the board.

NameTypeReqDescription
boundary_points
layerstring
netstringyes
priorityinteger

Structured output declared, but exposes no named fields.

No examples provided.

delete_item ~23

Delete an item from the board.

NameTypeReqDescription
item_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_board_design_settings ~73

Get board design rules and constraints. Returns: Dictionary with design settings (track widths, clearances, via specs). Example: >>> get_board_design_settings() {"track_width": 0.2, "via_diameter": 0.6, "via_drill": 0.3}

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_board_info ~71

Get board metadata (title, date, company, revision, comments). Returns: Dictionary with board metadata fields. Example: >>> get_board_info() {"title": "My PCB", "date": "2025-01-01", "company": "", "revision": "1.0"}

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_footprint ~45

Get detailed properties of a specific footprint by reference designator.

NameTypeReqDescription
referencestringyesFootprint reference designator (e.g., "U1", "R5").
NameTypeReqDescription
resultyes

No examples provided.

get_item_by_id ~24

Get item details by ID.

NameTypeReqDescription
item_idstringyes
NameTypeReqDescription
resultyes

No examples provided.

get_layers ~70

List all PCB layers with their properties. Returns: List of layer objects with id, name, type, visible, enabled. Example: >>> get_layers() [{"id": 0, "name": "Copper", "type": "signal", "visible": True, "enabled": True}]

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

get_net ~38

Get detailed information about a specific net by name.

NameTypeReqDescription
namestringyesNet name (e.g., "GND", "VCC").
NameTypeReqDescription
resultyes

No examples provided.

get_project ~48

Get current project information. Returns: Dictionary with project name and path. Example: >>> get_project() {"name": "my_design", "path": "/path/to/my_design.pro"}

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_selection ~13

Get the current selection.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

get_text_extents ~46

Calculate the bounding box of a text string.

NameTypeReqDescription
sizeintegerFont size in mm. Default 10.
textstringyesThe text string to measure.

Structured output declared, but exposes no named fields.

No examples provided.

get_version ~62

Get KiCad version and API version information. Returns: Dictionary with version strings and version match status. Example: >>> get_version() {"version": "9.0.1", "api_version": "9.0", "version_match": True}

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_footprints ~73

List all footprints on the board. Returns: List of footprint objects with reference, value, footprint type, position. Example: >>> list_footprints() [{"reference": "U1", "value": "ATmega328P", "footprint": "Package:DIP-8", ...}]

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_netclasses ~65

List all netclasses on the board. Returns: List of netclass objects with name and properties. Example: >>> list_netclasses() [{"name": "Default", "clearance": 0.2, "track_width": 0.25, ...}]

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_nets ~70

List all nets on the board. Returns: List of net objects with name, code, and netclass. Example: >>> list_nets() [{"name": "GND", "code": 0, "netclass": "Default"}, {"name": "VCC", ...}]

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_pads ~82

List all pads across all footprints. Returns: List of pad objects with footprint reference, number, net, position, size. Example: >>> list_pads() [{"footprint": "U1", "number": "1", "net": "VCC", "position": {"x": 0, "y": 0}, ...}]

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_texts ~68

List all text elements on the board. Returns: List of text objects with content, type, layer, position, size. Example: >>> list_texts() [{"text": "PCB Title", "type": "PCB_TEXT", "layer": "Silkscreen", ...}]

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_tracks ~80

List all tracks on the board. Returns: List of track objects with start/end positions, layer, net, width. Example: >>> list_tracks() [{"start": {"x": 0, "y": 0}, "end": {"x": 100, "y": 0}, "net": "VCC", ...}]

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_vias ~84

List all vias on the board. Returns: List of via objects with position, diameter, drill, net, layers. Example: >>> list_vias() [{"position": {"x": 100, "y": 50}, "diameter": 0.6, "drill": 0.3, "net": "GND"}]

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

list_zones ~75

List all zones (copper areas) on the board. Returns: List of zone objects with name, net, layer, fill mode, priority. Example: >>> list_zones() [{"name": "GND", "net": "GND", "layer": "Copper", "priority": 0}]

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

move_footprint ~41

Move a footprint to a new position by reference.

NameTypeReqDescription
referencestringyes
xnumberyes
ynumberyes

Structured output declared, but exposes no named fields.

No examples provided.

move_item ~38

Move an item to a new position.

NameTypeReqDescription
item_idstringyes
xnumberyes
ynumberyes

Structured output declared, but exposes no named fields.

No examples provided.

refill_zones ~17

Refill all zones on the board.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

rotate_footprint ~30

Rotate a footprint by reference.

NameTypeReqDescription
anglenumberyes
referencestringyes

Structured output declared, but exposes no named fields.

No examples provided.

rotate_item ~43

Rotate an item.

NameTypeReqDescription
anglenumberyes
center_xnumber
center_ynumber
item_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

save_board ~20

Save the board to a file.

NameTypeReqDescription
path

Structured output declared, but exposes no named fields.

No examples provided.

search_footprints ~42

Search footprints by reference designator, value, or footprint name.

NameTypeReqDescription
querystringyesSearch string to match against reference, value, or footprint name.
NameTypeReqDescription
resultarrayyes

No examples provided.

set_active_layer ~21

Set the active layer.

NameTypeReqDescription
layerstringyes

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the io.github.daedalus/mcp-kicad server?

io.github.daedalus/mcp-kicad is listed in the public MCP registry as io.github.daedalus/mcp-kicad. MCP server exposing KiCad PCB Editor functionality via IPC API. This page covers its PyPI package (mcp-kicad).

Is the io.github.daedalus/mcp-kicad server safe to use?

io.github.daedalus/mcp-kicad scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.daedalus/mcp-kicad server expose?

io.github.daedalus/mcp-kicad exposes 41 tools: connect_kicad, check_connection, get_board_info, get_layers, get_board_design_settings, and 36 more. Their descriptions and schemas cost roughly 2,179 tokens of context every time the server is loaded.

Is the io.github.daedalus/mcp-kicad server still maintained?

io.github.daedalus/mcp-kicad is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.daedalus/mcp-kicad server under?

io.github.daedalus/mcp-kicad declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.