DWG MCP Server logo

DWG MCP Server

DWG MCP Server MCP server inspects local DWG and DXF files through structured MCP tools and rendering.

Install DWG MCP Server

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

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "dwg-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@dmytro-prototypes/dwg-mcp-server"
      ],
      "env": {
        "DWG_MCP_ALLOWED_ROOTS": "YOUR_VALUE_HERE",
        "DWG_WORKER_BIN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

DWG MCP Server MCP server exposes local AutoCAD DWG and DXF files to MCP clients through tools for opening, querying, describing, and rendering drawings. It indexes each opened document in a dedicated worker, supports handle-based and filtered queries, and keeps source files unchanged. Use it when an agent needs structured drawing data, entity inspection, layout views, or PNG/SVG output rather than direct file editing.

Use cases

  • Inspect entities and properties in a DWG drawing
  • Query blocks, layouts, layers, and related objects
  • Render model-space or paper-space views
  • Compare selected in-memory property changes
  • Retrieve drawing objects by handle

Key features

  • DWG and DXF file access over MCP
  • Indexed object queries with filters and pagination
  • Type metadata and writable-property discovery
  • In-memory entity property updates
  • PNG and SVG rendering
  • Client-root and configured-root access control

Tools11

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

Verified live~1.8k 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 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 41d

What it can do

From the 11 tools this server returned when we ran it; 11 declare their own safety hints.

Can delete or modify data · 1Makes network requests · 1Read-only tools · 10
Network at startup5 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age211 days
Maintainers1

Observed 2026-10-21 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · @dmytro-prototypes/dwg-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars21Stargazers on the source repository.
npm downloads587Package downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Tools exposed11Callable tools this server registers over MCP.
Directory activity7 viewsConfig copies, upvotes, and views on AllMCPs.

How DWG MCP Server works

What DWG MCP Server does

DWG MCP Server MCP server provides MCP access to local DWG and DXF drawings. It lets an agent discover permitted folders, open a drawing, inspect its supported entity types, retrieve objects by handle, run structured queries, and render model space or paper-space views. The source file remains unchanged throughout normal use.

The server also exposes limited in-memory mutation for properties that the type metadata marks as writable. These changes apply only to the open document and are discarded when the document closes; the server does not save or overwrite the original drawing.

This fits the Architecture & Design category and is intended for agents that need drawing inspection, object discovery, relationship-aware queries, or visual output from CAD files.

How it works

A typical session begins with dwg.list_roots. The server uses roots supplied by the MCP client when available, or configured allowed directories as a fallback. The agent then calls dwg.open_file with a returned root URI and a path relative to that root. The response contains a documentId, which is required for later file-specific operations.

Opening a file starts a dedicated Rust worker and builds an in-memory index through LibreDWG. The index records handles, types, properties, and derived membership such as blocks, layouts, and model or paper space. dwg.get_objects performs direct handle lookup, while dwg.query_objects applies supported filters, scopes, relations, sorting, projections, and pagination against the index.

Rendering is compiled lazily on the first render request. The server can produce SVG or PNG output for model space, paper-space layouts, and layout viewports. Render results include diagnostics for unsupported entity types and generated-block fallbacks. After inspection, dwg.close_file releases the worker and discards in-memory changes.

Setup and configuration

Packaged releases provide a standalone native application. The npm package downloads the matching native build on first use, checks its SHA-256 checksum, caches it, and runs it directly. Docker and a separate Python installation are not required for this packaged path.

Native installer commands are provided for macOS Apple Silicon and Windows x64. MCP clients can also start the package with npx -y @dmytro-prototypes/dwg-mcp-server. Claude Code, Cursor, and Codex examples are included in the project documentation.

Clients that do not provide MCP roots can use DWG_MCP_ALLOWED_ROOTS, configured as a semicolon-separated list of absolute directories. When building from source, the project requires Rust, Python 3.11 or newer, and additional autotools on macOS or Linux. DWG_WORKER_BIN can point the Python host to a worker executable in a nonstandard location.

Tools and capabilities

The DWG MCP Server MCP server exposes these capabilities:

  • List accessible roots and globally supported drawing types.
  • List types found in a particular opened file.
  • Describe aliases, properties, and default fields for a type.
  • Fetch objects by handle while preserving request order and reporting missing handles.
  • Query by type, generic type, kind, handle, property values, block, layout, or space, with pagination and relation traversal.
  • Change writable properties on one entity in memory.
  • Discover renderable views and render them as PNG or SVG.

Limitations and notes

The DWG MCP Server MCP server does not write changes back to DWG or DXF files. In-memory property updates are validated against the type catalog and disappear when the document closes. Some writes have additional constraints, including coordinate and block-scaling rules; attributed block-reference updates are rejected when safe attribute transformation is unavailable.

Rendering covers common 2D geometry, text, MTEXT, hatch contours, approximated point-list entities, block references, generated dimension blocks, and paper-space viewports, but output can include coverage diagnostics for unsupported content. Automatic fitting rejects extreme sparse extents, while explicit regions can bound dense views.

Access is limited to files under client-provided or configured roots. Each opened document uses a worker process and should be closed when no longer needed. Official native artifacts target macOS Apple Silicon, Windows x64, and Linux on x64 or ARM64.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about DWG MCP Server

DWG MCP Server is an MCP server that connects AI clients to local DWG and DXF files. Its main tools open and close documents, list and describe drawing types, fetch or query objects, change supported properties in memory, and render model-space or paper-space views as PNG or SVG.

Install it with the project’s macOS Apple Silicon or Windows x64 installer, or start it through `npx -y @dmytro-prototypes/dwg-mcp-server`. The npm package downloads and verifies the matching native release, then an MCP client can launch the executable over stdio.

Yes, DWG MCP Server works with Cursor through a stdio MCP configuration. The documented setup uses `npx -y @dmytro-prototypes/dwg-mcp-server` as the command and does not require an additional path variable when the client provides MCP roots.

Use MCP client roots when the client supports them, or set `DWG_MCP_ALLOWED_ROOTS` to a semicolon-separated list of absolute directories. The agent must call `dwg.list_roots` first and open files using a returned root and a relative path.

No, it cannot save edits to the source file. `dwg.set_entity_properties` changes only properties marked writable on an opened in-memory document, and those changes are discarded when `dwg.close_file` is called.

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 PreviewDWG MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/dwg-mcp-server?style=directory)](https://allmcps.com/mcp/dwg-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/dwg-mcp-server"><img src="https://allmcps.com/api/badge/dwg-mcp-server?style=directory" alt="DWG MCP Server on AllMCPs" /></a>