CDT-KiCAD

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.

Supported target

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: KiCad MCP Server

Install and run

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.js

STDIO 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.

Use safely

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.

• Runtime tool contract.

• Generated inventory — current tools and categories.

• Task-oriented documentation.

• Stable release, installation and rollback.

• Known limitations.

• Contributor validation.

Attribution

MIT fork of mixelpixx/KiCAD-MCP-Server, upstream baseline v2.7.0. See LICENSE, ATTRIBUTION and fork release notes.