AutoCAD LT AutoLISP MCP Server

MCP server for AutoCAD LT v3.1: freehand AutoLISP execution, 8 consolidated tools, File IPC + ezdxf backends, focus-free dispatch, undo/redo, P&ID symbols, and robust IPC with ESC prefix and UTF-8 fallback. Companion agent skill. The autocad lt autolisp mcp server wraps that behind the Model Context Protocol, so an assistant can use it rather than through you.

What it actually does

MCP server for AutoCAD LT automation and headless DXF generation.

Configuration

You will need one environment variable: AUTOCAD_MCP_BACKEND. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• 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

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by hvkshetry; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the autocad lt autolisp mcp server does with a few real requests.