mcp · Global

qcad-mcp

fastmcp 3.4 server plus webapp for qcad pro architectural cad

Claim this listing

Represent qcad-mcp? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Data offered docs-verified: DXF/DWG parsing · DXF metadata (layers, entity counts, bounding box, blocks) · room detection, area calculation, door/window identification · 2D beam FEM analysis · DXF wall extrusion to 3D STL · SVG/PNG/PDF export · BIM wall data as JSON and IFC-shaped JSON · search and download of 4800+ CAD blocks from a part library · QCAD ECMAScript scripts gallery search · persistent CAD file depot with CRUD
Formats docs-verified: DXF · DWG · SVG · PNG · PDF · STL · BMP · OBJ · GLB · JSON · MCP stdio · MCP SSE · MCP HTTP (/mcp)
Access docs-verified: Free and open source under the MIT licence; no authentication documented. Some tools (e.g. plan_dimension, plan_text, plan_convert, plan_render) need a separate QCAD Professional licence (docs cite €50.40 single-user).

Use cases llm-inferred: Convert client-supplied DXF building plans into SVG previews and room/area schedules for a design report · Extrude DXF building walls to STL for 3D massing or visualisation review · Export wall geometry as IFC-shaped JSON for a BIM handoff · Batch-run plan_info or plan_analyse across a depot of drawings for a quick QA pass
Audience llm-inferred: BIM engineers · civils engineers · architects · CAD technicians

Constraints llm-inferred: Many tools (plan_dimension, plan_text, plan_hatch, plan_block_insert, plan_array, plan_convert, plan_wall_data, plan_render, plan_script, plan_exec, plan_agentic, plan_transpile) need QCAD Pro installed; the rest rely on the ezdxf engine. · Install and path guidance is Windows-oriented (Claude Desktop installer, start.ps1, %LOCALAPPDATA% depot); Linux and macOS setup is not documented. · Tool inventory mismatch: docs claim 42 tools and list plan_obj and plan_glb, which are absent from the ENTRY tool list (35 tools). · No authentication documented; plan_script and plan_exec run arbitrary ECMAScript in QCAD Pro, so expose only to trusted local clients. · The raster-to-DXF pipeline is marked Planned and is not available. · Default MCP client config points at a local SSE endpoint (localhost:11966/sse), so the backend must be running. · Companion servers (blender-mcp, freecad-mcp) are optional and only unlock extra features. · The docs table marks qcad_shutdown as READ-only despite it shutting the server down; check annotations before auto-approving tools. · Tool argument schemas are not in the docs; example argument names are inferred.

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Daily discovery 2026-10-15: GitHub search; verified via GitHub API. Tools/install/auth auto-extracted from README.

Metadata observed 14/10/2026 · daily-2026-10-15 (github-search)