puran-water/autocad-mcp

MCP server for AutoCAD LT automation and headless DXF generation.
Two backends, one API:
| Backend | Runtime | Requires AutoCAD? | Screenshot |
| File IPC | Windows Python | Yes — AutoCAD LT 2024+ (Windows) | Win32 PrintWindow |
| ezdxf | Any platform | No (headless) | matplotlib render |
The server exposes 8 consolidated tools (drawing, entity, layer, block, annotation, pid, view, system) over the MCP stdio transport. An MCP client (Claude Desktop, Claude Code, etc.) connects and drives AutoCAD through natural-language requests.
## Prerequisites (File IPC backend)
Windows 10/11 (the File IPC backend uses Win32 APIs for focus-free window messaging)
AutoCAD LT 2024 or newer — AutoLISP support was added in LT 2024 for Windows. AutoCAD LT for Mac exists but does not support AutoLISP.
Python 3.10+ (Windows native — not WSL Python)
uv package manager (install guide)
> The ezdxf headless backend works on any platform (Linux, macOS, WSL) for offline DXF generation without AutoCAD installed.
## Quick Start
### 1. Clone and install
powershell
git clone https://github.com/puran-water/autocad-mcp.git
cd autocad-mcp
uv sync
### 2. Load the LISP dispatcher in AutoCAD LT
Open AutoCAD LT and load mcpdispatch.lsp using APPLOAD:
1. Type APPLOAD in the AutoCAD command line
2. Browse to /lisp-code/mcpdispatch.lsp
3. Click Load
4. You should see: === MCP Dispatch v3.1 loaded === and Ready for commands via (c:mcp-dispatch)
> Tip: Add the file to your AutoCAD Startup Suite (in the APPLOAD dialog) so it loads automatically with every drawing.
### 3. Configure your MCP client
Add to your MCP client configuration (e.g. Claude Desktop claudedesktopconfig.json):
json
"mcpServers": {
"autocad-mcp": {
"command": "C:\\path\\to\\autocad-mcp\\.venv\\Scripts\\python.exe",
"args": ["-m", "autocadmcp"],
"env": { "AUTOCADMCPBACKEND": "fileipc" }
Key points:
The command must point to the Windows Python inside the project venv (not WSL python).
AUTOCADMCPBACKEND can be auto (default — tries File IPC, falls back to ezdxf), fileipc (requires AutoCAD), or ezdxf (headless only).
#### Running from WSL
If your MCP client runs in WSL (e.g. Claude Code), launch the server through cmd.exe so it runs as a native Windows process:
json
"mcpServers": {
"autocad-mcp": {
"type": "stdio",
"command": "cmd.exe",
"args": ["/d", "/s", "/c", "cd /d C:\\path\\to\\autocad-mcp && set AUTOCADMCPBACKEND=fileipc&& .venv\\Scripts\\python.exe -m autocadmcp"]
### 4. Verify
From your MCP client, call:
system(operation="status")
You should see backend: "fileipc" if AutoCAD is running, or backend: "ezdxf" for headless mode.
For native DWG work, require fileipc; the examples above disable headless fallback.
Verify DWGNAME, DWGPREFIX, CTAB and DBMOD with drawing.getvariables, then
inspect a screenshot before editing. status alone does not identify the active DWG.
Use a Windows-local working copy if Windows cannot access a WSL UNC path, and copy
saved deliverables back explicitly. Never use drawing.create to make a working copy:
it erases and purges the active drawing.
## Journaled native revisions
system(operation="revision", data={"action": "read", "drawing": "C:/work/copy.dwg",
"handles": ["ABCD"]}) reads native entities. The revision adapter supports bounded