Provides AI-driven PCB design automation for KiCAD, exposing 236 tools across 16 categories: schematic authoring and batch edits, hierarchical sheet management, symbol and footprint creation, board lifecycle and graphics/geometry editing, routing and Freerouting autorouting, DRC/clearance and layer constraints, net class assignment, library table CRUD, validation/lint/repair, common formats (PADS, Altium, Eagle, CADSTAR, Allegro .brd) import, JLCPCB/LCSC parts and datasheet lookup, and project state resources.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@CDT-KiCAD Run DRC on my PCB and export the Gerber files."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Generic ECAD execution provider for schematic, board, routing, library, export and DRC/ERC operations. Engineering design rules and professional approval belong to CDT_Engineer.
CDT release 0.1.3 (upstream baseline v2.7.0) · Provider kicad · Contract cdt-kicad-contract-v2.
239 tools registered; 236 indexed for keyword discovery and 3 discovery controls intentionally direct-only. 236 discoverable tools across 20 categories. All tools are directly callable; discovery is a search catalogue, not an execution gate.
Native acceptance is scoped to KiCad 10.0.6 on Windows 11, CLI/native execution. GUI IPC, other KiCad builds, Linux and macOS require separate acceptance. A source update or hosted CI PASS does not certify a new native deployment.
Related MCP server: RelayForge MCP
Use Node.js 20 and KiCad's Python environment with pcbnew available.
From a Windows PowerShell session:
git clone https://github.com/SlncTrZ/CDT-KiCAD.git
cd CDT-KiCAD
.\setup-windows.ps1
node dist/index.jsSTDIO is the default. Configure the MCP client using the client guide. For manual setup and optional OS lanes, see the platform guide and Windows troubleshooting.
HTTP is opt-in and requires deployment-managed KICAD_MCP_TOKEN.
Never put credentials in client arguments, URLs or committed configuration.
Call help, system_status and system_capabilities first. Pin the runtime
guide's contract_hash; verify the active backend/session and required capability.
An IPC-owned session must not silently downgrade to SWIG after connection loss.
Refuse unavailable capabilities and reconcile uncertain mutation outcomes before retrying.
Generated inventory — current tools and categories.
MIT fork of mixelpixx/KiCAD-MCP-Server,
upstream baseline v2.7.0. See LICENSE, ATTRIBUTION
and fork release notes.
This server cannot be deployed
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Verified component catalog over remote MCP: agents pick component ids and get a stamped project repo that builds. Connect at https://www.botkelp.com/mcp. Auth: MCP OAuth 2.1, or a Bearer bk_live_ API key; initialize and tools/list are open.
