A side-by-side look at the Figma Context MCP and KiCad MCP Pro MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figma Context MCP for architecture & design work as a local process; choose KiCad MCP Pro for architecture & design as a local process. You can also run both side by side in one mcpServers block.
FIGMA_API_KEY, PORT.get_figma_data, download_figma_images.kicad_list_tool_categories, kicad_get_tools_in_category, kicad_set_project.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 71/100 · Great | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | FIGMA_API_KEYPORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 16,019 | 141 |
| Directory activity | 7 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 2 | 24 |
| Full listing | View Figma Context MCP | View KiCad MCP Pro |
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/userkicad_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.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.
{
"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"
}
}
}
}
{
"mcpServers": {
"kicad-mcp-pro": {
"command": "uvx",
"args": [
"kicad-mcp-pro"
]
}
}
}