Figma Context MCP vs MCP CAD Studio
A side-by-side look at the Figma Context MCP and MCP CAD Studio 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 MCP CAD Studio 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 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.
Choose MCP CAD Studio when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You want tools like
studio_ui, list_models, load_model.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 71/100 · Great | 60/100 · Good |
| 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,009 | 3 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 2 | 13 |
| Full listing | View Figma Context MCP | View MCP CAD Studio |
Tools & capabilities
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
MCP CAD Studio tools 13
studio_uiOpen the interactive CAD Studio. Use this when the user asks to view or work with a model visually.list_modelsList the CAD models currently saved in this studio.load_modelLoad a saved CAD model, including the modelId, current revision, complete editable parametric definition, and render mesh. Call this before update_model or delete_model.create_modelCreate a separate new CAD model from a declarative parametric shape tree. Do not use this to modify an existing model; load it and call update_model instead. Supports primitives, extrusions, transforms, mesh input, and boolean operations.generate_modelGenerate a built-in parametric template: bracket, pipe, gear, enclosure, or bolt. To revise a previously generated model, pass its modelId and expectedRevision to regenerate it in place. Omit modelId only when the user wants a separate new model.update_modelModify an existing saved model in place while preserving its modelId. Use patches for small edits (example: replace /shape/size/0), or shape to replace the complete definition. Load the model first and pass its expectedRevision. Never call create_model merely to revise an existing model.validate_shapePreflight a complete parametric shape without saving it. Reports static polygon/mesh topology errors and warnings, then asks the CAD kernel to verify the solid. Use this before create_model or update_model for complex shapes.transform_modelApply an incremental translation, Euler rotation in degrees, or scale to a CAD model.boolean_modelsCreate a new model by union, difference, or intersection of two or more saved models.duplicate_modelCreate an editable copy of a saved CAD model.delete_modelPermanently delete one saved CAD model. Call list_models or load_model first to identify the exact modelId, and pass expectedRevision when available to avoid deleting a newer edit.import_modelImport an STL or OBJ model from text or base64 data and save it in the studio.- +1 more on the listing page
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.
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"
}
}
}
}
MCP CAD Studio
{
"mcpServers": {
"mcp-cad-studio": {
"command": "npx",
"args": [
"-y",
"mcp-cad-studio"
]
}
}
}
Frequently asked questions
Figma Context MCP is categorized under Architecture & Design and uses a local stdio subprocess. MCP CAD Studio belongs to Architecture & Design and uses a local stdio subprocess. Pick Figma Context MCP for architecture & design work and MCP CAD Studio 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.
Figma Context MCP is listed as free. Auth: api key required. MCP CAD Studio has no declared pricing — check the project's own site. 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 glips-figma-context-mcp and mcp-cad-studio as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figma Context MCP has a quality signal of 71/100 (Great) with 6 views, 0 installs and 16,009 GitHub stars. MCP CAD Studio has 60/100 (Good) with 1 views, 0 installs and 3 GitHub stars.