{"id":"puran-water-autocad-mcp","name":"autocad-mcp","af_score":62.8,"security_score":24.8,"reliability_score":37.5,"what_it_does":"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).","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.","last_evaluated":"2026-03-30T13:38:45.268316+00:00","has_mcp":true,"has_api":false,"auth_methods":[],"has_free_tier":false,"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."],"error_quality":0.0}