Qcad MCP vs Figwright
A side-by-side look at the Qcad MCP and Figwright MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Qcad MCP for architecture & design work over a hosted endpoint; choose Figwright 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 Qcad MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
QCAD_MCP_DEPOT. - You want tools like
plan_depot, plan_info, plan_create.
Choose Figwright 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 want tools like
Read, Write, Grounding.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 56/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | QCAD_MCP_DEPOT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 17 | 1,159 |
| Directory activity | 4 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 36 | 3 |
| Full listing | View Qcad MCP | View Figwright |
Tools & capabilities
Qcad MCP tools 36
plan_depotList files in the persistent CAD depot with metadataplan_infoDXF metadata: layers, entity counts, bounding box, blocksplan_createCreate DXF from primitives (line, rect, circle, text, polyline)plan_to_svgDXF → SVG preview with layer filteringplan_extrudeDXF walls → 3D STL mesh (configurable height/thickness)plan_exportDXF → SVG/PNG/PDF (ezdxf or QCAD Pro)plan_analyseRoom detection, area calculation, door/window identificationplan_measureMeasure distances and lengths in a DXFplan_wall_dataExtract wall segments as BIM-ready JSON (QCAD Pro)plan_beam_analysis2D beam FEM analysis (numpy, no QCAD needed)plan_dimensionAdd aligned/linear/angular/radial dimensions (QCAD Pro)plan_textAdd text annotations (QCAD Pro)- +24 more on the listing page
Figwright tools 3
Readselection, document and node inspection, styles, variables, components, fonts, prototype reactions and flows, motion (animation) state, screenshots, original image-fill assets, PDF export, and video export of animated frames (MP4 / GIF / WebM); plus `list_files` / `use_file` for working across more…Writecreate and edit frames, text, shapes (lines, polygons, stars, boolean operations, flattening), auto-layout, alignment and distribution, effects, images (as a new layer or into an existing layer's fill), styles, variables (including importing a team library's variables and styles, and switching a fr…Grounding`get_design_context` for faithful, de-duplicated design context, and `component_map` / `token_map` / `icon_map`, which join Figma data to your codebase so codegen reuses what you already have; plus `design_diff`, which reports what changed in a design against a saved baseline so you update only the…
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.
Qcad MCP
{
"mcpServers": {
"qcad-mcp": {
"url": "http://localhost:11966/sse"
}
}
}
Figwright
{
"mcpServers": {
"awdr74100-figwright": {
"command": "npx",
"args": [
"-y",
"@figwright/mcp@latest"
]
}
}
}
Frequently asked questions
Qcad MCP is categorized under Architecture & Design and uses a remote HTTP/SSE transport. Figwright belongs to Architecture & Design and uses a local stdio subprocess. Pick Qcad MCP for architecture & design work and Figwright 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.
Qcad MCP has no declared pricing — check the project's own site. Figwright is listed as free. Auth: no auth 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 qcad-mcp and awdr74100-figwright as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Qcad MCP has a quality signal of 56/100 (Good) with 4 views, 0 installs and 17 GitHub stars. Figwright has 69/100 (Great) with 6 views, 0 installs and 1,159 GitHub stars.