KiCad MCP Server (IPC API)
Provides tools to query, edit, and manage PCB boards in a running KiCad instance, including component placement, routing, zone filling, layer control, selection, and export to various formats (Gerber, PDF, SVG, 3D, etc.).
Click on "Install 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., "@KiCad MCP Server (IPC API)list all components on the board"
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.
KiCad MCP Server (IPC API)
MCP server that controls a running KiCad 9+ instance via the official IPC API and kicad-python (kipy).
Board edits appear immediately in the KiCad UI — no reload required. The server wraps the full Board + Project IPC surface available in kicad-python 0.7.1 (KiCad 10).
Prerequisites
KiCad 9.0+ running with a PCB open
IPC API enabled: Preferences → Plugins → Enable IPC API Server
Python 3.10+
Related MCP server: kicad-mcp
Install
cd kicad_mcp_server_ipc
python3 -m venv .venv
source .venv/bin/activate
pip install -e .Run
kicad-mcp-ipc
# or
python -m kicad_mcp_ipcCursor / Grok MCP configuration
{
"mcpServers": {
"kicad-ipc": {
"command": "/path/to/kicad_mcp_server_ipc/.venv/bin/kicad-mcp-ipc"
}
}
}Optional environment variables:
Variable | Description |
| Path to KiCad IPC socket (auto-detected if unset) |
| Auth token from KiCad when launched as plugin |
| Request timeout in ms (default: 5000) |
Architecture
server.py → FastMCP entry point
services/api.py → Unified KiCadAPI facade (board + project + session)
services/export.py → Export jobs via IPC RunJob, kicad-cli fallback
tools/definitions.py → Tool definitions mapped to API methods
tools/registry.py → Categories, search, JSON schemas
tools/register.py → Dynamic MCP tool registration
layers.py / serialize.py → Layer aliases and JSON serializationDesign principles:
Service layer — MCP tools call
KiCadAPI, notkipydirectlyRegistry — tool metadata (category, parameters, schema) is separate from handlers
Transactions — edits use
begin_commit/push_commitfor undo supportMeta tools — discover and invoke tools without loading all schemas upfront
Tools (77 total)
Use list_tool_categories, search_tools, or get_tool_schema to explore the full set at runtime.
Meta / discovery
Tool | Description |
| Browse all categories and tool names |
| Search by name, description, or category |
| Get parameter schema for a specific tool |
| Run any tool by name with a JSON arguments object |
Session (5)
ping_kicad, get_kicad_status, list_open_documents, get_kicad_version, run_kicad_action
Board query (21)
Read-only inspection: get_board_info, get_board_size, get_board_as_string, get_selection_as_string, list_components, get_component, list_tracks, list_vias, list_pads, list_nets, list_zones, list_groups, list_dimensions, list_board_text, list_board_shapes, list_barcodes, get_items_by_id, get_items_by_net, get_connected_items, get_stackup, get_title_block
Board edit (16)
save_board, revert_board, place_component, move_component, rotate_component, delete_component, route_trace, add_via, add_copper_pour, refill_zones, add_board_text, add_board_outline, add_mounting_hole, set_board_size, delete_items_by_id, set_title_block
Layers (8)
get_layer_list, get_visible_layers, get_active_layer, set_active_layer, set_visible_layers, get_copper_layer_count, set_enabled_layers, get_layer_name
Selection (4)
get_selection, add_to_selection, remove_from_selection, clear_selection
Geometry (2)
get_item_bounding_box, hit_test
Origins (2)
get_board_origin, set_board_origin
Appearance (1)
get_editor_appearance
Project (4)
get_net_classes, get_text_variables, set_text_variables, expand_text_variables
Export (10)
Manufacturing and documentation output. Each export tries the IPC RunJob API first, then falls back to kicad-cli if needed.
Tool | Output |
| Gerber copper/silk/mask layers |
| Excellon drill files |
| PDF plot |
| SVG plot |
| DXF |
| STEP, GLB, STL, VRML, etc. |
| Pick-and-place centroid files |
| IPC-2581 package |
| ODB++ package |
| Board statistics report |
Response format
All tools return JSON strings:
{
"success": true,
"components": [...],
"count": 42
}On failure:
{
"success": false,
"message": "No PCB board is open in KiCad. Open a .kicad_pcb file first.",
"operation": "get_board_info"
}Limitations (kicad-python 0.7.1)
The following are not exposed because they are unavailable or unstable in the installed IPC bindings:
Schematic editing (Schematic class exists; IPC commands not wired in 0.7.1)
get_design_rules/import_netlist(KiCad 11+)set_editor_appearance_settings(read-only for safety)run_kicad_action(unstable KiCad internal API)
Project layout
src/kicad_mcp_ipc/
├── server.py # MCP entry point
├── connection.py # KiCad IPC connection singleton
├── services/
│ ├── api.py # KiCadAPI facade
│ └── export.py # Export via IPC jobs + kicad-cli
├── tools/
│ ├── definitions.py # All tool definitions
│ ├── registry.py # Category/search/schema registry
│ └── register.py # Dynamic FastMCP registration
├── layers.py # Layer name ↔ enum helpers
├── serialize.py # kipy object → JSON helpers
├── board.py # Backward-compat alias for KiCadAPI
├── errors.py
└── utils.pyLicense
Uses KiCad IPC via kicad-python, which is licensed under the GPL. This MCP server is a separate client application that communicates with KiCad over IPC.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lmaag182/kicad_mcp_server_ipc'
If you have feedback or need assistance with the MCP directory API, please join our Discord server