AutoCAD MCP Server
Related Servers
Alternatives to AutoCAD MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables users to control supported CAD applications through AI assistants using the Model Context Protocol, supporting drawing, layers, entities, blocks, files, exports, and natural-language automation.-
- FlicenseNot gradedqualityDmaintenanceEnables users to control CAD software like AutoCAD, GstarCAD, and ZWCAD through natural language instructions via the Model Context Protocol. It supports automated drawing of shapes, layer management, and saving designs to DWG files without manual interface interaction.2-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to control supported CAD applications through the Model Context Protocol, allowing drawing, layer/entity/block management, data export, and file/session operations via natural-language or direct tool calls.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to control AutoCAD, ZWCAD, GstarCAD, and BricsCAD through the Model Context Protocol, supporting drawing, layer/entity/block management, data export, file operations, and natural-language CAD task automation.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to control AutoCAD, ZWCAD, GstarCAD, and BricsCAD through the Model Context Protocol, supporting drawing, layer, entity, block, file, export, and session operations via unified tools or natural-language commands.-
- AlicenseAqualityDmaintenanceEnables automated CAD operations via natural language, supporting both AutoCAD LT on Windows and headless DXF generation on any platform.8MIT
TDQS
Scored across 8 tools
Each top-level group targets a distinct domain (drawing, view, entity, layer, block, annotation, pid, system), so selection is mostly clear. Minor overlap exists where entity.create_mtext and annotation.create_text both create text, and pid's specialized insert_valve/instrument/pump/tank parallel generic entity creation, but descriptions keep the boundaries workable.
Namespaces and operations use a consistent snake_case verb_noun pattern (create_line, set_current, insert_symbol, add_flow_arrow). A few bare verbs (list, count, get, copy, move, erase) deviate slightly but remain conventional and readable within their groups.
Eight well-grouped top-level tools is a sensible scope for a large CAD domain, avoiding a flat blizzard of 60+ operations. The grouping is heavy (each group bundles many sub-operations), but that is a reasonable encapsulation rather than a mismatch.
The surface covers the full CAD lifecycle: file create/open/save/export/plot, entity CRUD with transforms and boolean-style ops, layer and block management with attributes, annotation, and a dedicated P&ID workflow. Undo/redo and system diagnostics round it out with no obvious dead ends.