kicad-mcp (Huaqiu Electronics)

MCP serverCommunity

A KiCad server built on the IPC API that runs one instance per editor: schematic, PCB, symbol or footprint. By Huaqiu Electronics.

25 starsUpdated 7 months agoGitHub data from 5 Nov 2026

At a glance

Type: MCP server
Works with: KiCad
How it connects: Drives a running copy of the tool
Access: Not stated in its documentation
Tool versions: Not stated in its documentation
Operating systems: Not stated in its documentation
Needs a KiCad licence: No
Transport: Local (stdio)
AI clients documented: Claude Code, VS Code, Cherry Studio
Licence: MIT
Language: Python

What it can do

Connects to KiCad through its IPC API rather than the SWIG bindings.
Starts separate servers for the schematic, PCB, symbol and footprint editors through an --editor-type option, so each client sees only the tools for that editor.
Runs straight from PyPI with uvx, with no clone or build step.

Limitations

The README doesn't list the tools, the supported KiCad versions or the operating systems.

Install

uvx kicad-mcp --editor-type schematic

Source: github.com/Huaqiu-Electronics/kicad-mcp

{
	"mcpServers": {
		"Kicad-Schematic-MCP": {
			"type": "stdio",
			"command": "uvx",
			"args": [
				"kicad-mcp",
				"--editor-type",
				"schematic"
			]
		},
		"Kicad-PCB-MCP": {
			"type": "stdio",
			"command": "uvx",
			"args": [
				"kicad-mcp",
				"--editor-type",
				"pcb"
			]
		}
	},
	"inputs": []
}

Source: github.com/Huaqiu-Electronics/kicad-mcp

MCP servers and skills run code on your computer. Review the source before installing.

AI-generated models, drawings and results must be checked by a qualified engineer before use.