Model Context Protocol (MCP) server for KiCad electronic design automation (EDA) files
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"iflow-mcp-kicad-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# KiCad MCP Server 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. ## Table of Contents - [Prerequisites](#prerequisites) - [Installation Steps](#installation-steps) - [Understanding MCP Components](#understanding-mcp-components) - [Feature Highlights](#feature-highlights) - [Natural Language Interaction](#natural-language-interaction) - [Documentation](#documentation) - [Configuration](#configuration) - [Development Guide](#development-guide) - [Troubleshooting](#troubleshooting) - [Contributing](#contributing) - [Future Development Ideas](#future-development-ideas) - [License](#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: ```bash # 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: ```bash # 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: ```ba…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.