# KiCad MCP Pro Server [Health: Active]

**Category:** 📐 Architecture & Design  
**Repository:** https://github.com/oaslananka/kicad-mcp-pro  
**GitHub Stars:** 229  
**Views:** 14  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/kicad-mcp-pro-server

## Description
MCP server for KiCad project setup, PCB edits, schematic work, validation, and exports.

## Tools
Capabilities this server exposes over MCP:

- **kicad_list_tool_categories** — List all available tool categories and capabilities. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
- **kicad_get_tools_in_category** — Get tool names in a category, optionally filtered by maturity.
- **kicad_set_project** — Set the active KiCad project directory and file paths. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
- **kicad_get_project_info** — Show the currently configured KiCad project paths. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
- **project_design_workflow** — 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.
- **project_get_next_action** — Return the next high-priority action derived from the current project gate.
- **kicad_get_version** — Get KiCad version information and current connection status. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
- **pcb_get_board_summary** — Summarize the current board. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
- **pcb_visual_qa** — 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.
- **pcb_get_stackup** — Show the current stackup. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
- **pcb_get_design_rules** — Read the active board design rules file when available. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
- **sch_get_symbols** — List all schematic symbols, optionally from a child sheet. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
- **sch_get_bounding_boxes** — 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.
- **sch_get_connectivity_graph** — Summarize the active schematic as a textual net connectivity graph.
- **sch_visual_qa** — 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.
- **lib_verify_component_contract** — 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.
- **lib_get_bom_with_pricing** — Generate a live BOM summary with unit and extended pricing.
- **run_erc** — Run schematic electrical rule checks. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
- **run_drc** — Return full DRC report with PCB violations, unconnected items, and courtyard issues.
- **validate_design** — Run DRC and ERC and summarize readiness. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
- **project_quality_gate** — Run the full project quality gate across schematic, PCB, DFM, and parity checks.
- **validate_footprints_vs_schematic** — Compare PCB footprint references against the schematic symbol references. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.
- **dfm_run_manufacturer_check** — Run a manufacturer-aware DFM review using the active bundled profile.
- **kicad_get_server_info** — Return versioned server information and capability diagnostics for clients. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "kicad-mcp-pro-server": {
    "command": "uvx",
    "args": ["kicad-mcp-pro"]
  }
}
```

## Documentation

## What KiCad MCP Pro Server does

KiCad MCP Pro Server exposes KiCad workflow operations through the Model Context Protocol. It works with local project files and can report KiCad connection and version information, configure the active project directory and file paths, and return server capability diagnostics.

The available review surface covers both schematic and PCB data. Agents can inspect board summaries, layer stackups, design rules, schematic symbols, estimated symbol bounding boxes, and net connectivity. The server also provides headless readability checks for PCB and schematic geometry, including off-board footprints, silkscreen or body overlaps, crowded labels, off-sheet objects, and title-block gaps.

Validation tools combine KiCad checks with project-level comparisons. They can run DRC and ERC, compare schematic references with PCB footprints, verify component symbol-to-footprint contracts, perform manufacturer-aware DFM review, and summarize overall design readiness. BOM generation includes unit and extended pricing.

## How it works

Project setup begins by selecting the active KiCad project and its relevant paths. The project workflow tool models work as Planner, Builder, Verifier, Fixer, and Release phases. An agent can pass completed phases to identify the next ready phase, its required action, quality gates, and any human approval point. A separate action tool derives the next high-priority task from the current project gate.

The default profile starts with a bounded set of read-only review tools. Build mode supports controlled write operations, release mode is intended for manufacturing handoff with human gates, and expert or full profiles are available for advanced trusted clients. The listed read-only inspection and validation tools can operate directly on project files; PCB and schematic visual QA does not require rendering.

The server supports stdio and Streamable HTTP transports. Streamable HTTP serves the MCP endpoint at `/mcp` by default and can be moved with `KICAD_MCP_MOUNT_PATH`.

## Setup and configuration

The command-line package can be started with `uvx`:

```bash
uvx kicad-mcp-pro quickstart
uvx kicad-mcp-pro tray
uvx kicad-mcp-pro dashboard --open
uvx kicad-mcp-pro --transport streamable-http --port 3334
```

A local dashboard can be opened at `http://127.0.0.1:3334/ui` with:

```bash
uvx kicad-mcp-pro dashboard --host 127.0.0.1 --port 3334 --open
```

The project also offers a desktop application that starts the Python dashboard automatically. Client configuration depends on the chosen MCP transport. Telemetry and error reporting are disabled by default, with optional OpenTelemetry configuration available.

## Tools and capabilities

- Discover tool categories and filter tools by maturity.
- Set and inspect the active KiCad project paths.
- Inspect PCB summaries, stackups, design rules, schematic symbols, bounding boxes, and connectivity.
- Run headless PCB and schematic visual QA from file geometry.
- Check component contracts, footprint-reference parity, DRC, ERC, design readiness, and project quality gates.
- Generate BOM pricing and run manufacturer-aware DFM checks.
- Drive a typed, phase-based project workflow with next-action guidance.

## Limitations and notes

The server is intended as a first-pass design and review assistant, not an automated sign-off authority. DRC and ERC, along with the export pipeline, use KiCad’s own engines and remain important for authoritative validation. Signal-integrity, power-integrity, EMC, and thermal analysis are first-order closed-form estimates rather than substitutes for field solvers, electromagnetic or FEA simulation, or formal approval.

The PCB visual QA tool complements rather than replaces DRC, particularly for courtyard and silkscreen clipping sign-off. Schematic bounding boxes are heuristic estimates because exact symbol extents are not exposed through the file API. Live component sourcing uses the JLCPCB public catalog by default; Nexar, DigiKey, and Mouser require configured API credentials.

_Full upstream README: https://allmcps.com/mcp/kicad-mcp-pro-server/readme_

