AutoCAD MCP Ultra
# AutoCAD MCP Ultra
**Industrial-grade AutoCAD MCP server for AI agents** — Dual live engines (ActiveX COM for full AutoCAD + File-IPC AutoLISP for AutoCAD LT 2024+) + Headless ezdxf + ISO GD&T + P&ID process drafting + Rhino.Inside Grasshopper Battery Bridge.
## Key Features
- **AutoCAD 2024+ Universal Support**: Full AutoCAD (COM) and AutoCAD LT (AutoLISP IPC).
- **Rhino.Inside Grasshopper Battery Bridge**: Built-in adapter for all 87+ AutoCAD Tab Grasshopper components with TrackedBake idempotent live updates.
- **ISO/DIN Mechanical Standards**: ISO 1101 GD&T, ISO 129 dimensions, ISO 286 fits (`H7`), Involute gear generator with section A-A, DIN 6885 keyed bores, ISO 7200 title blocks.
- **Process & P&ID Engineering**: Dedicated P&ID symbols for pumps, valves, instruments, vessels, and automated piping routing.
- **Token Efficiency & Discovery Mode**: Low token idle overhead (~356 tokens) with semantic search over 158 CAD commands and 87 GH batteries.
- **5-Step Agent Quality Loop**: Preflight -> Plan -> Critique (0-100 score) -> Refine -> Finalize with SHA-256 delivery manifest.
TDQS
Scored across 162 tools
Several tools are near-duplicates (block_insert vs entity_create_block_ref, system_run_lisp vs lisp_execute_code), and save/export and selection/query families overlap heavily (drawing_save vs drawing_save_as vs drawing_export_dxf; selection_window/polygon/filter/entity_select_smart/analysis_select_*). At 162 tools, an agent cannot reliably pick the intended tool without reading every description.
The server mostly uses readable snake_case and strong domain prefixes (drawing_, entity_, layer_, block_, dimension_), but the verb/object order and granularity vary: block_list vs block_create_from_entities, entity_create_block_ref vs block_insert, selection_window vs entity_select_smart, and drawing_audit vs validation_check vs drawing_critique. It is not chaotic, but the consistency is only partial.
162 tools is far beyond the 25+ threshold and well into extreme-mismatch territory for a single server. The surface mixes core CAD primitives with highly specialized one-off workflows (gear drawings, P&ID, Grasshopper, ISO title blocks), forcing enormous tool-selection overhead.
Core CAD lifecycle coverage is broad: files, entities, layers, blocks, text, dimensions, hatches, layouts, viewports, selection, transactions, validation, and export are all represented, and most create/read/update/delete paths are complete. Minor gaps exist (no rename for layers/blocks, no dimension text editing, limited geometry editing for polylines/splines), but agents can usually work around them by delete/recreate.