AutoCAD 2024 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cad_instancesA | List running AutoCAD 2024 processes registered with this MCP server, including PID and active drawing. Use this before cad_connect when multiple AutoCAD windows are open. |
| cad_connectA | Bind subsequent MCP calls to one specific AutoCAD process. This prevents operations from being routed to the wrong drawing when multiple instances are running. |
| cad_statusA | Check the AutoCAD 2024 bridge, active document, product version, and current drawing state. |
| cad_capabilitiesA | Return the exact 0.0.3 feature matrix, limits, coordinate conventions, and verified export behavior without contacting AutoCAD. |
| cad_documentC | Create, open, save, save-as, close, activate, or list AutoCAD drawings. Paths must be absolute local paths. |
| cad_inspectC | Read drawing metadata, system variables, layers, blocks, layouts, styles, or entities. Use handles returned here for precise edits. |
| cad_solidB | Create editable AutoCAD 3DSOLID primitives or apply boolean union, subtract, and intersect operations. Coordinates are WCS and one request is atomic. |
| cad_measureB | Measure selected entities: extents, curve length, planar area, 3D solid volume, centroid, and optional mass from density. |
| cad_drawB | Atomically create 2D entities, annotations, hatches, dimensions, and block references. Angles are radians and coordinates use the current UCS unless otherwise stated. |
| cad_editA | Atomically edit entities selected by exact handles or a constrained filter. Supports properties, move, copy, rotate, scale, mirror, and erase. |
| cad_layerC | Create, update, delete, rename, set current, isolate, or restore drawing layers. |
| cad_blockC | Create a block definition from entities, insert a block, redefine it, or import a DWG as a block. |
| cad_layoutC | Create, rename, delete, activate, configure, or list paper-space layouts and their plot settings. |
| cad_exportC | Export the active drawing or a layout to DWG, DXF, PDF, DWF, SVG, PNG, or JPEG. The destination must be an absolute path. |
| cad_viewC | Zoom, pan, orbit, switch named views, regenerate, or capture a preview image. |
| cad_undoB | Undo or redo completed MCP edit operations in the active drawing. |
| cad_commandA | Run an AutoCAD command sequence only when a specialized MCP tool cannot express the operation. Commands are blocked unless explicitly allowlisted in the plugin configuration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Tools are mostly distinct and target different AutoCAD operations (drawing, editing, layers, layouts, etc.). Some conceptual overlap exists between cad_edit and cad_block (entity manipulation), and cad_draw vs cad_command (command execution), but the descriptions clarify the boundaries.
All tool names follow a consistent prefix_verb or prefix_noun pattern (e.g., cad_view, cad_undo, cad_connect). The 'cad_' prefix and single-word action label are uniform throughout, making the set predictable and easy to parse.
17 tools is slightly on the higher side but reasonable for a feature-rich AutoCAD automation server. Each tool corresponds to a meaningful domain area (view, edit, draw, measure, export, etc.) and no tool appears redundant.
The surface covers core drawing lifecycle, entity manipulation, layers, blocks, layouts, and exports. Minor gaps exist: no explicit tool for deleting entities (though cad_edit supports erase via handles), and no dedicated tool for attaching xrefs or managing external references. These are workarounds rather than critical omissions.