AutoCAD MCP Ultra
Related Servers
Alternatives to AutoCAD MCP Ultra
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to automate AutoCAD LT and create DXF files headless, with tools for drawing, entity, layer, block, annotation, PID, and system operations.16MIT
- AlicenseAqualityCmaintenanceEnables an AI assistant to conversationally control Autodesk AutoCAD, drawing, inspecting, and editing plans, and includes a cross-platform DXF engine that runs without AutoCAD on macOS and Linux. It exposes tools for rendering views as images, batching geometry, blocks, and structures, measuring and checking plans, and undoing whole batches.12MIT
- AlicenseBqualityAmaintenanceProduction-grade AutoCAD automation server enabling real-time CAD control via COM and headless DXF operations through 87 tools, including drawing creation, entity modification, layer management, and batch processing, designed for AI agent integration via the Model Context Protocol.2100443 PyPI83MIT
- AlicenseAqualityDmaintenanceEnables LLMs like Claude to create and edit AutoCAD drawings via natural language, supporting both headless DXF generation and live AutoCAD LT connection through file-based IPC.9MIT
- AlicenseAqualityDmaintenanceEnables automated CAD operations via natural language, supporting both AutoCAD LT on Windows and headless DXF generation on any platform.8MIT
- FlicenseBqualityAmaintenanceNatural-language MCP bridge for AutoCAD 2024. Enables users to inspect and edit DWG drawings, manage layers, entities, layouts, styles, and system variables; draw 2D geometry and 3D solids; perform measurements and transactional edits; and export to DWG, STL, PDF, DWF, SVG, or raster formats through a local named-pipe connection.211-
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.