Qcad MCP logo

Qcad MCP

Process DXF/DWG floor plans with MCP tools for previews, analysis, exports, extrusion, and QCAD Pro automation.

Install Qcad MCP

Pick your client, then add it in one click or paste the config.

SSE (Remote)
Server URL
http://localhost:11966/sse

Remote servers are added in the app, not the config file: Customize β†’ Connectors β†’ Add custom connector, then paste this URL.

Overview

The qcad-mcp MCP server connects AI clients to DXF/DWG processing, persistent CAD storage, and optional QCAD Pro automation. It can inspect, create, measure, analyse, modify, render, export, and extrude CAD plans through MCP tools, with a REST API for uploads, downloads, depot management, and tool execution. Use it for programmatic floor-plan workflows, SVG previews, STL generation, room analysis, or drafting operations that require QCAD Pro. Basic parsing, rendering, extrusion, and analysis use ezdxf, while several advanced operations require a local QCAD Pro installation.

Use cases

  • Inspect DXF floor-plan structure and metadata
  • Generate SVG previews and STL wall meshes
  • Analyse rooms, areas, doors, and windows
  • Maintain a persistent CAD file depot
  • Automate QCAD Pro drafting operations

Key features

  • DXF/DWG inspection and creation
  • SVG, PNG, PDF, and STL generation
  • Room, measurement, and beam analysis
  • Persistent CAD depot with REST CRUD
  • QCAD Pro scripting and drafting tools
  • CAD block and script library access

Tools36

What Qcad MCP lets your agent do. Expand a tool for its parameters.

Self-reported~501 tokens of context

Security & health

What it can reach and how reliably it runs β€” from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 46d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks β€” not a rating.

GitHub stars17Stargazers on the source repository.
Last commit12d agoMost recent push to the default branch.
Tools exposed36Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Qcad MCP works

What qcad-mcp does

The qcad-mcp MCP server exposes CAD operations for DXF and DWG workflows. It stores files in a persistent depot, lets an MCP client inspect drawing structure, and supports creating DXF files from lines, rectangles, circles, text, and polylines. Floor plans can be converted to SVG previews, measured, analysed for rooms and areas, or extruded into STL meshes with configurable wall height and thickness.

The server also includes a REST API. It supports file upload and download, depot listing and CRUD operations, health and status checks, MCP tool execution, live log streaming, settings management, and chat through Ollama. A web interface provides pages for the depot, viewer, extrusion, analysis, layers, blocks, scripts, batch jobs, pipelines, logs, and settings.

How the qcad-mcp MCP server works

The default CAD depot is %LOCALAPPDATA%\\qcad-mcp\\depot on Windows and persists across restarts. Set QCAD_MCP_DEPOT to use another location. The backend listens on port 11966 and the dashboard uses port 11967. MCP clients connect through the SSE endpoint shown in the repository configuration:

config.json
{
  "mcpServers": {
    "qcad": {
      "url": "http://localhost:11966/sse",
      "transport": "sse"
    }
  }
}

Most core operations use the Python ezdxf engine. QCAD Pro is an optional dependency for operations such as DWG conversion, high-fidelity rendering, dimensions, annotations, hatches, block insertion, arrays, wall-data extraction, and ECMAScript execution. The qcad_status tool reports whether QCAD Pro is installed, running, and which version is available. Beam analysis uses NumPy and does not require QCAD Pro.

Tools and capabilities

The qcad-mcp MCP server provides read, mutation, and status tools covering the following workflows:

  • List depot files and inspect layers, entities, bounds, and blocks with plan_depot and plan_info.
  • Create, modify, measure, export, preview, and analyse DXF plans with plan_create, plan_modify, plan_measure, plan_export, plan_to_svg, and plan_analyse.
  • Generate STL meshes from walls with plan_extrude, or produce BIM-oriented wall JSON with plan_wall_data when QCAD Pro is available.
  • Add dimensions, text, hatches, blocks, and array patterns through QCAD Pro tools.
  • Convert DXF and DWG files, render SVG/PDF/BMP output, and run QCAD ECMAScript using the relevant QCAD Pro tools.
  • Search and download CAD blocks from a library described as containing more than 4,800 entries.
  • Search and download QCAD ECMAScript scripts from the gallery or Gist.
  • Run 2D beam finite-element analysis with plan_beam_analysis.
  • Use plan_agentic for natural-language-to-ECMAScript workflows and plan_transpile for AutoLISP-to-QCAD ECMAScript translation; both require QCAD Pro and are MCP-only tools.

The quick-start workflow uses just bootstrap to synchronize Python and frontend dependencies, followed by start.ps1 to start the backend and frontend on Windows.

Limitations and notes

QCAD Pro is required for the tools explicitly marked as QCAD Pro features; the repository does not present those operations as available through ezdxf alone. The REST API and dashboard expose additional server functionality, but MCP clients should use the configured SSE endpoint for MCP tool access. The raster-to-DXF process described in the repository is planned rather than a currently listed MCP tool, so it should not be treated as built-in support.

Reviews

No reviews yet β€” be the first to share how it worked for you.

Frequently Asked Questions about Qcad MCP

qcad-mcp is an MCP server that connects AI clients to DXF/DWG files, the ezdxf engine, a persistent CAD depot, and optional QCAD Pro. Its main tools create, inspect, measure, analyse, modify, render, export, and extrude plans, while additional tools support QCAD scripting, CAD blocks, and REST-based file management.

Run `just bootstrap`, then start the Windows services with `start.ps1`. The bootstrap step synchronizes Python and frontend dependencies, while the start script launches the backend and frontend and opens the browser.

Connect over SSE at `http://localhost:11966/sse` using the `qcad` server name and `sse` transport. The repository configuration uses this endpoint for MCP clients.

No, not for every operation. Core parsing, rendering, extrusion, and analysis use ezdxf, and beam analysis uses NumPy. QCAD Pro is required for marked features such as DWG conversion, advanced rendering, drafting operations, ECMAScript execution, agentic workflows, and AutoLISP translation.

CAD files are stored by default in `%LOCALAPPDATA%\\qcad-mcp\\depot` on Windows. Set `QCAD_MCP_DEPOT` to configure a different depot location; files persist across server restarts and system reboots.

Related MCP servers

Add a badge to your READMEShow it’s listed β€” live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewQcad MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/qcad-mcp?style=directory)](https://allmcps.com/mcp/qcad-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/qcad-mcp"><img src="https://allmcps.com/api/badge/qcad-mcp?style=directory" alt="Qcad MCP on AllMCPs" /></a>