CDT AutoCAD Provider
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CDT_AUTOCAD_BACKEND | No | Backend selection: ezdxf (default) or com | ezdxf |
| CDT_AUTOCAD_AUTH_TOKEN | Yes | Required for every HTTP launch (credentials must be supplied by deployment/runtime configuration) | |
| CDT_AUTOCAD_COM_PROGID | No | COM ProgID; default AutoCAD.Application | AutoCAD.Application |
| CDT_AUTOCAD_UNDO_DEPTH | No | ezdxf snapshot undo depth; default 10; 0 disables undo/redo | 10 |
| CDT_AUTOCAD_COM_TIMEOUT | No | Live COM deadline in seconds; default 60 | 60 |
| CDT_AUTOCAD_CALL_TIMEOUT | No | Ordinary headless deadline in seconds; default 120 | 120 |
| CDT_AUTOCAD_ALLOWED_PATHS | No | Path-list of allowed CAD/PDF roots; defaults to launch directory | launch directory |
| CDT_AUTOCAD_MAX_DXF_BYTES | No | Maximum input CAD file size at the provider boundary; default 50 MiB | 50 MiB |
| CDT_AUTOCAD_RENDER_TIMEOUT | No | Headless render/PDF deadline in seconds; default 300 | 300 |
| CDT_AUTOCAD_ALLOW_REMOTE_HTTP | No | Must be true in addition to auth for non-loopback bind | |
| CDT_AUTOCAD_COM_ATTACH_POLICY | No | COM attach policy: attach_only (default) or attach_or_start | attach_only |
| CDT_AUTOCAD_TRANSACTION_DEPTH | No | Maximum tracked transaction depth; default 8 | 8 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
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 50 tools
Most tools are clearly grouped by domain prefix (document, object, layer, viewport, etc.), which helps an agent distinguish them. However, the object_* and entity_create_* groups could be confused since both deal with drawing entities, and hatch_create/dimension_* do not follow the same entity_create_* pattern.
The naming is mostly consistent with lowercase snake_case and predictable domain prefixes like document_, object_, layer_, and viewport_. Minor deviations include bare verbs like undo/redo, adjective-style names like dimension_linear, and view_zoom_extents/view_zoom_window using verb-in-middle phrasing.
50 tools is well beyond the typical well-scoped range and will create significant context overhead for an agent. While the AutoCAD domain is broad, this surface feels oversized and would benefit from consolidation or tighter scoping.
The tool set covers core document lifecycle, drawing maintenance, object manipulation, entity creation, layers, blocks, layouts, viewports, transactions, and undo/redo. Minor gaps like no explicit layer deletion, block editing, or document_close exist, but agents can likely work around them with the available object and property tools.