KiCad MCP Pro Server vs Figma Context MCP
A side-by-side look at the KiCad MCP Pro Server and Figma Context MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose KiCad MCP Pro Server for architecture & design work as a local process; choose Figma Context MCP for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose KiCad MCP Pro Server when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
KICAD_MCP_MOUNT_PATH. - You want tools like
kicad_list_tool_categories, kicad_get_tools_in_category, kicad_set_project.
Choose Figma Context MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FIGMA_API_KEY, PORT. - You want tools like
get_figma_data, download_figma_images.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 65/100 · Great | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | KICAD_MCP_MOUNT_PATH | FIGMA_API_KEYPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 145 | 16,047 |
| Directory activity | 6 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 24 | 2 |
| Full listing | View KiCad MCP Pro Server | View Figma Context MCP |
Tools & capabilities
KiCad MCP Pro Server tools 24
kicad_list_tool_categoriesList all available tool categories and capabilities. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.kicad_get_tools_in_categoryGet tool names in a category, optionally filtered by maturity.kicad_set_projectSet the active KiCad project directory and file paths. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.kicad_get_project_infoShow the currently configured KiCad project paths. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.project_design_workflowReturn the professional PCB design workflow as a typed phase state machine. Lays out the canonical Planner -> Builder -> Verifier -> Fixer -> Release sequence, with the high-level tool and the quality gates each phase must pass. Pass the phases already finished in ``completed_phases``; the tool marks them COMPLETE, reports the first remaining phase as READY (the current step) with its next action and gates, and flags when a human gate is required. Read-only and headless — use it to drive an autonomous design run step by step.project_get_next_actionReturn the next high-priority action derived from the current project gate.kicad_get_versionGet KiCad version information and current connection status. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.pcb_get_board_summarySummarize the current board. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.pcb_visual_qaHeadless PCB readability QA: off-board parts, silk and body overlap. A fast, file-backed first pass that runs without a live KiCad: it flags footprints whose body leaves the board outline, reference designators that collide on the silkscreen, and overlapping footprint bodies — directly from the ``.kicad_pcb`` geometry. It complements (does not replace) the authoritative DRC run, which remains the sign-off check for courtyard and silk clipping. Returns JSON with an overall PASS/INFO/WARN status and per-finding refs/positions.pcb_get_stackupShow the current stackup. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.pcb_get_design_rulesRead the active board design rules file when available. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.sch_get_symbolsList all schematic symbols, optionally from a child sheet. This KiCad MCP Pro tool supports production EDA automation workflows for MCP clients.- +12 more on the listing page
Figma Context MCP tools 2
get_figma_dataGet comprehensive Figma file data including layout, content, visuals, and component informationdownload_figma_imagesDownload SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/user
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
KiCad MCP Pro Server
{
"mcpServers": {
"kicad-mcp-pro-server": {
"command": "uvx",
"args": [
"kicad-mcp-pro"
],
"env": {
"KICAD_MCP_MOUNT_PATH": "YOUR_KICAD_MCP_MOUNT_PATH_HERE"
}
}
}
}
Figma Context MCP
{
"mcpServers": {
"glips-figma-context-mcp": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Frequently asked questions
KiCad MCP Pro Server is categorized under Architecture & Design and uses a local stdio subprocess. Figma Context MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick KiCad MCP Pro Server for architecture & design work and Figma Context MCP for architecture & design.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
KiCad MCP Pro Server is listed as free. Auth: no auth required. Figma Context MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kicad-mcp-pro-server and glips-figma-context-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, KiCad MCP Pro Server has a quality signal of 65/100 (Great) with 6 views, 0 installs and 145 GitHub stars. Figma Context MCP has 71/100 (Great) with 9 views, 0 installs and 16,047 GitHub stars.