DWG MCP Server

DWG MCP Server

DWG MCP Server is an MCP server for inspecting AutoCAD DWG files with AI agents and assistants. It provides read-only access to drawing contents as queryable objects. Agents can open a DWG, inspect available types, fetch objects by handle, and query properties, scopes, and references.

Quick Start

Use DWG MCP Server from the MCP client of your choice. The npm package launches the published Docker image. The Docker launcher mounts $HOME by default. For drawings outside $HOME, set DWG_MCP_DOCKER_MOUNTS.

If your MCP client, AI agent, or test harness does not support MCP roots, set DWG_MCP_ALLOWED_ROOTS to the folders that should be accessible.

Codex

codex mcp add dwg-mcp \
  --env DWG_MCP_ALLOWED_ROOTS="$HOME" \
  -- npx -y @dmytro-prototypes/dwg-mcp-server

Codex does not currently provide MCP client roots to stdio MCP servers. Configure explicit allowed roots for the folders that contain your drawings.

Claude

claude mcp add --scope user --transport stdio dwg-mcp -- npx -y @dmytro-prototypes/dwg-mcp-server

Claude Code provides MCP roots, so no extra path variable is usually needed.

Cursor

{
  "mcpServers": {
    "dwg-mcp": {
      "command": "npx",
      "args": ["-y", "@dmytro-prototypes/dwg-mcp-server"]
    }
  }
}

Exposed Tools

| Tool | Purpose | | --- | --- | | dwg.list_roots | List folders available for DWG access. | | dwg.open_file | Open a DWG from an available folder and return a documentId. | | dwg.close_file | Close an opened document and release its worker process. | | dwg.list_types | List the globally supported DWG types known to the backend. | | dwg.list_file_types | List only the types that are present in a specific opened DWG. | | dwg.describe_type | Describe a supported type, including its properties and default projection. | | dwg.get_objects | Fetch specific objects by handle, preserving the requested order and reporting missing handles. | | dwg.query_objects | Query objects with filters, scopes, relation traversal, sorting, projection, and pagination. |

A typical flow is:

1. Discover available folders with dwg.list_roots.
2. Open a file from one of those folders with dwg.open_file.
3. Inspect supported or file-local types with dwg.list_types, dwg.list_file_types, or dwg.describe_type.
4. Fetch known handles with dwg.get_objects or search the drawing with dwg.query_objects.
5. Close the session with dwg.close_file.

Architecture

Runtime model

In the packaged deployment, DWG MCP Server is a stdio MCP server implemented in Python and typically run inside a Linux container. The Python host exposes the MCP tools, validates file access, and manages document sessions.

Each dwg.open_file call starts a dedicated Rust dwg-worker process for that DWG and returns a host-side documentId. All later file-scoped calls use that document id. dwg.close_file terminates the worker for that session.

Worker and query model

The Rust worker speaks newline-delimited JSON over stdin and stdout. When it opens a DWG through LibreDWG, it first builds an in-memory indexed document. That upfront indexing step is central to the design: the server pays the cost once when the file is opened, then answers later requests against the index instead of rescanning the DWG each time.

The indexed model stores object handles, kinds, type names, generic types, summary and full properties, and derived block, layout, and space membership. It also stores supported type metadata such as aliases, default projections, and property definitions.

When you request full object records, responses also include that derived membership under extendedData, including container block, layout, and model or paper space when known.

dwg.get_objects is direct lookup by handle. dwg.query_objects runs over indices for handle, type, generic type, kind, exact property values, block, layout, and space, then applies filters, scopes, relation traversal, sorting, projection, and pagination. This is what makes queries over blocks, layers, layouts, references, and related objects practical on an opened drawing.

Access and packaging

DWG files must be opened from roots listed by dwg.list_roots. The server first asks the MCP client for roots. If the client, AI agent, or test harness does not support MCP roots, configure explicit allowed roots:

python3 -m dwg_mcp_server --allowed-root "$HOME/Downloads"

or:

DWG_MCP_ALLOWED_ROOTS="$HOME/Downloads;$HOME/Documents/dwg" \
python3 -m dwg_mcp_server

DWG_MCP_ALLOWED_ROOTS is an authorization fallback for clients without roots. It should be a semicolon-separated list of absolute directories.

Docker is separate from MCP roots: roots authorize access, mounts make host folders visible inside the container. The npm Docker launcher mounts $HOME by default. For drawings outside $HOME, set DWG_MCP_DOCKER_MOUNTS.

For clients without MCP roots, DWG_MCP_ALLOWED_ROOTS is also used as the Docker mount list unless DWG_MCP_DOCKER_MOUNTS is set.

The Docker image itself unpacks a prebuilt LibreDWG bundle, builds the Rust worker against it, and copies only the static-linked worker plus schema files into the final Python runtime image.

Build and Test From Source

Local source builds use the vendored third_party/libredwg submodule by default.

Prerequisites

• Rust toolchain
• Python 3.11 or newer
• Docker, if you want to build or run the container image
• autotools for local LibreDWG builds on macOS or Linux (autoreconf, aclocal, automake, autoconf, make)

Bootstrap

git submodule update --init --recursive
bash scripts/build-libredwg.sh

Prebuilt LibreDWG bundles

CI and Docker builds use a Git LFS LibreDWG bundle instead of rebuilding LibreDWG on every run. The current CI bundle target is:

prebuilt/libredwg/x86_64-unknown-linux-gnu.tar.gz

Refresh it only when the LibreDWG submodule or native build inputs change:

bash scripts/build-linux-libredwg-prebuilt.sh x86_64-unknown-linux-gnu

For local macOS debugging, keep using bash scripts/build-libredwg.sh and the local Rust build; the Linux prebuilt archive is for CI and Docker.

Build and test

cargo test --workspace
bash scripts/run-e2e-tests.sh

Run the MCP host locally

The Python host looks for dwg-worker under target/release or target/debug. If you want a release build explicitly:

cargo build -p dwg-worker --release

Then run the MCP host:

PYTHONPATH=server/src python3 -m dwg_mcp_server

If the worker binary lives somewhere else, set DWG_WORKER_BIN to that executable.

Build and run with Docker

Build the image:

bash scripts/build-docker-mcp-server.sh

Run the server and expose specific host folders read-only:

DWG_MCP_DOCKER_MOUNTS="$HOME/Documents;$HOME/Desktop/dwg" \
bash scripts/run-docker-mcp-server.sh

Use this when your client supports MCP roots but the container still needs those host root paths mounted read-only.

For clients without MCP roots, set DWG_MCP_ALLOWED_ROOTS instead:

DWG_MCP_ALLOWED_ROOTS="$HOME/Documents;$HOME/Desktop/dwg" \
bash scripts/run-docker-mcp-server.sh

Use this when your AI agent or harness does not provide MCP roots. The server will allow those directories, and the Docker launcher will mount the same directories read-only unless DWG_MCP_DOCKER_MOUNTS is set.

By default, the Docker launcher mounts DWG_MCP_ALLOWED_ROOTS, then ~/Documents when no roots are configured. Access is still authorized by MCP client roots or explicit allowed roots; Docker mounts only make those paths visible inside the container.

Clean rebuild

Remove local build artifacts, Python caches, and the local Docker image:

bash scripts/clean-build-artifacts.sh

To also wipe the host LibreDWG build under third_party/libredwg:

bash scripts/clean-build-artifacts.sh --with-libredwg

Official MCP Registry

Registry metadata lives in server.json under the GitHub-authenticated name io.github.dimitrovakulenko/dwg-mcp-server.

Before publishing a new registry version:

1. Publish the matching npm package version from npm/.
2. Confirm npm/package.json contains the same mcpName as server.json.
3. Run the manual Publish MCP Registry GitHub Actions workflow, or run:

mcp-publisher login github
mcp-publisher publish

The registry validates the published npm package, so server.json must point to an npm version that already exists on the public npm registry.

License

This project is licensed under the GNU General Public License v3.0. See LICENSE for the full license text.