AutoCAD MCP

Connects Claude to your CAD drawings. You talk to Claude in plain language and it queries, draws, organizes and exports the drawing.

• Windows: drives the CAD that is open: AutoCAD (full, not LT), BricsCAD, ZWCAD or GstarCAD.

• Mac, AutoCAD LT, or no CAD at all: edits .dxf files directly (and .dwg with the free ODA File Converter installed).

How to use (for people who draw)

1. Open the drawing in your CAD (on a Mac, just tell Claude the file's path).

2. Ask for what you need in Claude, for example:

   • "Which drawing is open and what unit is it in?"

   • "Build the area schedule for the rooms and place the table next to the plan."

   • "How many doors and windows are there? Split them by type and save it for Excel."

   • "Monte o quadro de esquadrias com largura, altura e peitoril."

   • "Monte o quadro de áreas do terreno e confira TO 60 %, CA 2 e TP 15 %."

   • "Export all sheets to PDF." / "Exporte para PDF todas as pranchas dos desenhos desta pasta."

   • "Put the layers in the AsBEA standard."

   • "I selected some text. Move all of it to layer ARQ-___-TXT with height 0.20."

   • "Draw the walls of a 4 x 3 m room, 15 cm thick, starting at 0,0."

3. In Claude Desktop the + button holds ready-made shortcuts: Area schedule, Quantity takeoff, Door and window schedule, Site areas and indices, Export sheets to PDF, Review layers and Review drawing.

Tips

• Select objects in the CAD and say "what I selected".

• Each request is one undo step: press U in the CAD, or ask "undo that".

• Claude never saves the file unless you ask.

• "The CAD is busy": press Esc in the CAD and ask again.

Related MCP server: Civil3D MCP Server

Install

Claude Desktop (Windows and Mac)

Download autocad-mcp-<version>.mcpb from the latest release and double-click it. Claude Desktop shows the settings (read-only, projects folder, layer standard, number format) and installs it. It needs uv, which fetches Python and the dependencies the first time.

Claude Code

/plugin install autocad --marketplace gabrielbsandim/autocad-mcp

By hand

With uv installed, clone the repository and add to the Claude Desktop config (%APPDATA%\Claude\claude_desktop_config.json on Windows, ~/Library/Application Support/Claude/claude_desktop_config.json on a Mac):

{
  "mcpServers": {
    "autocad": {
      "command": "uv",
      "args": ["run", "--directory", "C:\\path\\to\\autocad-mcp", "--no-dev", "autocad-mcp"],
      "env": { "AUTOCAD_MCP_LAYER_STANDARD": "asbea" }
    }
  }
}

Then quit Claude Desktop completely and open it again.

What it can do (23 tools)

Every tool has a title and says whether it only reads, changes the drawing, or can destroy something, so Claude asks before the risky ones.

Made for Brazilian offices

• Quadro de áreas with the room names and numbers found inside each outline, totals in m², labels A = 12,50 m² placed inside U and L shaped rooms.

• Quadro de esquadrias: doors and windows found by block name or layer, grouped by code (TIPO, CODIGO...), with width, height and sill read from attributes (LARGURA, ALTURA, PEITORIL or 80x210, in m, cm or mm); without a width attribute, it is measured from the block.

• Quadro de áreas do terreno for the permit: lot area, built area per floor (each floor plan's region), projection, permeable area, TO, CA and TP, each checked against the limits of the zoning law you give.

• Titles and headers in Portuguese (QUADRO DE ÁREAS, AMBIENTE, ÁREA (m²)...), numbers as 1.234,50 and CSV with ; so Excel opens them as numbers. AUTOCAD_MCP_LOCALE=en-US switches all of it to English.

• AsBEA layers, including the ones the site table reads (ARQ-___-TER, ARQ-___-ACO, ARQ-___-APJ, ARQ-___-PER).

Layer standards

Two come built in: AsBEA (asbea, Brazilian: ARQ-ALV, ARQ-POR, ARQ-___-CTA...) and AIA (aia: A-WALL, A-DOOR...). Each layer has a color, linetype, lineweight, plot flag and aliases, the old names that should become it (PAREDE*, WALL*, A-WALL...), so a drawing from either template, or from no template, is converted. Copy asbea_layers.json, edit it to your office's names and point AUTOCAD_MCP_LAYER_STANDARD at the copy.

Live CAD or file mode

The live CAD is found by its automation name: AutoCAD, BricscadApp.AcadApplication, ZWCAD.Application and GCAD.Application, in that order; AUTOCAD_MCP_PROGID picks one. The clones copy the AutoCAD object model, so the same calls apply; run scripts/live_check.py with yours open to confirm it before relying on it.

AutoCAD LT has no automation interface, so with LT use file mode: save as DXF (or install ODA File Converter for DWG). Driving LT live through AutoLISP was left out on purpose: LT only accepts it typed into its command line, so it would mean faking keystrokes into the user's window, which cannot be tested and breaks when the user clicks. The ODA converter is free for personal use; check its license before using it in a company.

Security

• No network. Claude talks to the server over stdin/stdout; the server talks to the CAD through the local Windows COM interface. No port is opened.

• No arbitrary code. No tool runs AutoLISP, scripts or free-form commands. The one exception is undo, which sends exactly _.UNDO n.

• System variables: only a closed list can be changed. No SECURELOAD, TRUSTEDPATHS or similar.

• Files: saving never overwrites without overwrite=True, and opening is read-only by default. Only full local paths: network shares, mapped network drives and URLs are refused, because opening one would send your Windows credentials to that host. AUTOCAD_MCP_ALLOWED_DIRS confines every read and write.

• CSV: cells Excel would run as a formula get a leading apostrophe.

• Undo: every change is grouped. If it fails halfway, what it already did is undone, so the drawing is never left half-changed. Every action, including failures, is logged locally.

• Busy or stuck CAD: reads retry while the CAD is busy; changes never retry (a repeated write would draw twice) and wait for it to be idle. No answer in 60 s returns an error instead of hanging Claude.

• Read-only mode refuses every change, save and export.

• Never starts the CAD by itself.

• Pinned dependencies, locked with hashes in uv.lock.

See PRIVACY.md: nothing is collected or sent anywhere.

Settings

The action log is at %LOCALAPPDATA%\autocad-mcp\actions.log on Windows and ~/.local/state/autocad-mcp/actions.log elsewhere.

Development

src/autocad_mcp/
  server.py          instructions for Claude, tool registration and shortcuts (prompts)
  cad.py             the CAD thread: backend choice, busy retries for reads, timeouts
  com.py             live backend: AutoCAD and its clones over Windows COM, friendly errors
  filecad.py         file backend: the same object model over ezdxf, for DXF/DWG without a CAD
  acad.py            object helpers, writes with undo and rollback, scans that report skips, log
  rooms.py           room outlines, names, areas
  takeoff.py         block counts, lengths and hatch areas per layer
  reports.py         schedules (rooms, blocks, lengths) shared by tables and CSV
  files.py           path checks and Excel-safe CSV
  geometry.py        pure geometry (areas with arcs, interior points, offsets)
  units.py           INSUNITS and pt-BR / en-US number formatting
  layer_standard.py  pure layer-standard logic; standards/ holds AsBEA and AIA
  openings.py        door and window schedule
  site.py            site areas and TO, CA, TP
  render.py          sheets to SVG or PDF without a CAD
  tools/             one area per file
tests/               every tool end to end over MCP against a real DXF, on Windows, macOS and Linux
scripts/stdio_check.py  the server as Claude runs it: a child process over stdio (--live for the CAD)
scripts/live_check.py   every tool against the CAD that is open, on a new drawing closed without saving

uv sync --extra dev --extra pdf
uv run pytest
uv run python scripts/stdio_check.py
uv run python scripts/live_check.py     # Windows, with the CAD open

A new tool goes in the right module under tools/, registered with spec(title, READ | WRITE | DESTRUCTIVE). Reads use await cad.run(fn); drawing changes use await acad.change("name", args, body), which handles read-only mode, waits for an idle CAD, groups the undo, rolls back a failure and logs; other writes (files) use await acad.act("name", args, fn). Loops over objects go through acad.Scan, so an unreadable object is reported, never silently dropped. Expected errors raise AcadError with a clear message.

Releases: push a v* tag and the workflow tests, packs the .mcpb and publishes it.

Inspired by codesknight/AutoCAD-MCP (COM + stdio architecture) and felixalmesberger/AUTOCAD-MCP (document management). No code was copied.