{"id":"puran-water-autocad-mcp","name":"autocad-mcp","homepage":null,"repo_url":"https://github.com/puran-water/autocad-mcp","category":"devtools","subcategories":[],"tags":["mcp","autocad","autolisp","cad","dxf","stdio","windows","automation","ezdxf","ipc"],"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).","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"],"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.","alternatives":["AutoCAD/AutoCAD LT scripting via built-in command-line automation and/or official SDKs","ezdxf-only pipelines for DXF generation without AutoCAD automation","Other MCP servers or custom tooling that wraps native CAD APIs/automation frameworks"],"af_score":62.8,"security_score":24.8,"reliability_score":37.5,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:38:45.268316+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"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":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"MIT-licensed project; no pricing model indicated in provided data."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":62.8,"security_score":24.8,"reliability_score":37.5,"mcp_server_quality":85.0,"documentation_accuracy":75.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":95.0,"rate_limit_clarity":0.0,"tls_enforcement":0.0,"auth_strength":10.0,"scope_granularity":0.0,"dependency_hygiene":55.0,"secret_handling":70.0,"security_notes":"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.","uptime_documented":0.0,"version_stability":55.0,"breaking_changes_history":40.0,"error_recovery":55.0,"idempotency_support":"false","idempotency_notes":"Some operations mutate drawings (create/open/undo/redo, entity CRUD, purge). No explicit idempotency guarantees are stated; repeated calls may accumulate changes depending on operation sequencing.","pagination_style":"none","retry_guidance_documented":false,"known_agent_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."]}}