Atlas / MCP servers / lamaalrajih / KiCad

KiCadCAUTION

Name: KiCad
Author: lamaalrajih

mcp/lamaalrajih/kicad

MCP server by lamaalrajih · Audited 2026-09-30

⚑ Report / re-scan Source ↗

Model Context Protocol server for KiCad on Mac, Windows, and Linux

Verdict

CAUTION

Grade

Trust score

83 /100

Exposed tools

18 17r · 1w · 0d

Transport

—

License

MIT

Stars

525

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

This guide will help you set up a Model Context Protocol (MCP) server for KiCad. While the examples in this guide often reference Claude Desktop, the server is compatible with any MCP-compliant client. You can use it with Claude Desktop, your own custom MCP clients, or any other application that implements the Model Context Protocol.

Prerequisites
Installation Steps
Understanding MCP Components
Feature Highlights
Natural Language Interaction
Documentation
Configuration
Development Guide
Troubleshooting
Contributing
Future Development Ideas
License

Prerequisites

macOS, Windows, or Linux
Python 3.10 or higher
KiCad 9.0 or higher
uv 0.8.0 or higher
Claude Desktop (or another MCP client)

Installation Steps

1. Set Up Your Python Environment

First, let's install dependencies and set up our environment:

# Clone the repository
git clone https://github.com/lamaalrajih/kicad-mcp.git
cd kicad-mcp

# Install dependencies – `uv` will create a `.venv/` folder automatically
# (Install `uv` first: `brew install uv` on macOS or `pipx install uv`)
make install

# Optional: activate the environment for manual commands
source .venv/bin/activate

2. Configure Your Environment

Create a .env file to customize where the server looks for your KiCad projects:

# Copy the example environment file
cp .env.example .env

# Edit the .env file
vim .env

In the .env file, add your custom project directories:

# Add paths to your KiCad projects (comma-separated)
KICAD_SEARCH_PATHS=~/pcb,~/Electronics,~/Projects/KiCad

3. Run the Server

Once the environment is set up, you can run the server:

Read from source at commit bd20e7b5fe0bOBSERVED · 2026-09-30

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code

claude mcp add kicad-mcp -- uvx kicad-mcp

claude-desktop

{
  "mcpServers": {
    "kicad-mcp": {
      "command": "uvx",
      "args": [
        "kicad-mcp"
      ]
    }
  }
}

Exposed tools (18)

17 read · 1 write · 0 destructive.

Tool	Risk	Description
`analyze_bom`	read	Analyze a KiCad project
`analyze_project_circuit_patterns`	read	Identify circuit patterns in a KiCad project
`analyze_schematic_connections`	read	Analyze connections in a KiCad schematic.
`export_bom_csv`	read	Export a Bill of Materials for a KiCad project.
`extract_project_netlist`	read	Extract netlist from a KiCad project
`extract_schematic_netlist`	read	Extract netlist information from a KiCad schematic.
`find_component_connections`	read	Find all connections for a specific component in a KiCad project.
`generate_pcb_thumbnail`	read	Generate a thumbnail image of a KiCad PCB layout using kicad-cli.
`generate_project_thumbnail`	read	Generate a thumbnail of a KiCad project
`generate_validation_report`	read	Generate a comprehensive validation report for a KiCad project.
`get_drc_history_tool`	read	Get the DRC check history for a KiCad project.
`get_project_structure`	read	Get the structure and files of a KiCad project.
`identify_circuit_patterns`	read	Identify common circuit patterns in a KiCad schematic.
`list_projects`	read	Find and list all KiCad projects on this system.
`open_project`	read	Open a KiCad project in KiCad.
`run_drc_check`	write	Run a Design Rule Check on a KiCad PCB file.
`validate_project`	read	Basic validation of a KiCad project.
`validate_project_boundaries`	read	Validate component boundaries for an entire KiCad project.

Trust audit

CAUTIONgrade B · trust 83/100 Install with care. The audit found things worth knowing before you trust its output.

Layer	What it checks	Result
L0	Provenance & inventory	PASS
L1	Static analysis of the code	WARN
L2	Instruction surface (what it tells the agent)	PASS
L3	Class-specific surface	PASS
L4	Behavioural (sandbox)	SKIPPED

What the source does

Filesystem: declared (6 observation(s))
Network: none-observed
Shell: none-observed
Dependencies: pinned
Secrets in source: none-found

Findings (10)

MEDIUMFilesystem / path · fs.system_paths · CWE-22, CWE-59

kicad_mcp/tools/drc_impl/cli_drc.py:158

"/usr/local/bin/kicad-cli",

MEDIUMFilesystem / path · fs.system_paths · CWE-22, CWE-59

kicad_mcp/utils/kicad_api_detection.py:55

"/usr/local/bin/kicad-cli",

MEDIUMFilesystem / path · fs.system_paths · CWE-22, CWE-59

kicad_mcp/utils/kicad_cli.py:166

"/usr/local/bin/kicad-cli",

MEDIUMFilesystem / path · fs.system_paths · CWE-22, CWE-59

kicad_mcp/utils/kicad_cli.py:182

"/usr/local/bin/kicad-cli",