autocad-mcp
Provides an MCP stdio server that automates AutoCAD LT (Windows) via AutoLISP dispatch using a File IPC backend, and alternatively generates/render DXF headlessly via an ezdxf backend. Exposes consolidated MCP tools for drawing/entity/layer/block/annotation/P&ID/view/system operations, plus an execute_lisp escape hatch (File IPC only).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No authentication/authorization described; server appears to rely on local connectivity (stdio) and caller control. The execute_lisp tool enables arbitrary AutoLISP execution via File IPC, which is a major risk if the agent input is not fully trusted. TLS is not applicable (stdio/MCP local transport). IPC uses filesystem temp JSON files; ensure directory permissions are restricted. Dependency list includes pywin32 only for win32; overall security posture depends on code quality not assessed here.
⚡ Reliability
Best When
You have MCP-capable agent tooling and either (a) AutoCAD LT 2024+ on Windows for File IPC automation, or (b) a headless DXF pipeline on any platform using ezdxf.
Avoid When
You need robust authentication/authorization for remote callers, or you cannot control who can invoke the server (especially execute_lisp), or you require strict operational safety guarantees for arbitrary CAD changes.
Use Cases
- • AI-assisted AutoCAD LT drafting/automation in Windows environments
- • Headless DXF generation and rendering for workflows that don't require AutoCAD
- • Automating repetitive CAD operations (entities, layers, blocks, views, screenshots/plots)
- • Programmatic insertion of P&ID symbols and diagram elements
- • Integrating CAD operations into an MCP-capable agent (e.g., Claude Desktop/Code)
Not For
- • Production multi-tenant SaaS usage without strong sandboxing/isolation
- • Non-Windows AutoCAD LT automation (AutoLISP not supported on AutoCAD LT for Mac)
- • Operations that require interactive GUI-only workflows beyond what the IPC/LISP dispatcher supports
- • Highly secure environments that cannot tolerate arbitrary AutoLISP execution when enabled
Interface
Authentication
No user-facing authentication described. Access appears to be determined by local process/stdio connectivity and the caller's ability to run the server/configure it. execute_lisp enables arbitrary AutoLISP execution (File IPC), increasing the need for controlling trust boundaries.
Pricing
MIT-licensed project; no pricing model indicated in provided data.
Agent Metadata
Known Gotchas
- ⚠ File IPC backend requires Windows + AutoCAD LT 2024+; ezdxf backend is headless but lacks some features (e.g., plot_pdf, undo/redo, certain entity ops like offset/fillet/chamfer).
- ⚠ execute_lisp can execute arbitrary AutoLISP (File IPC only); agents should not be granted untrusted autonomy without strict input controls.
- ⚠ IPC directory (AUTOCAD_MCP_IPC_DIR) must match between Python server and mcp_dispatch.lsp; mismatches likely cause failures.
- ⚠ Backend selection via AUTOCAD_MCP_BACKEND=auto depends on AutoCAD being running for file_ipc; otherwise it falls back to ezdxf.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for autocad-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.