CDT AutoCAD Provider
# CDT-AutoCAD
Generic AutoCAD execution provider for MCP clients. It owns native CAD execution,
state verification and recovery; engineering design rules belong to CDT_Engineer.
Provider `0.4.2` · Contract `autocad-generic-v1` · 87 public tools.
Native acceptance is scoped to AutoCAD 2027 full on Windows x64. The headless DXF
lane has separate capabilities; other AutoCAD versions need their own acceptance.
## Install and run
Use Python 3.12 and the platform lock from this checkout. On Windows:
```powershell
python -m venv .venv
.\.venv\Scripts\python.exe -m pip install pip==26.1.2
.\.venv\Scripts\python.exe -m pip install -r pylock.windows.toml
.\.venv\Scripts\python.exe -m pip install --no-deps --no-build-isolation .
$env:CDT_AUTOCAD_BACKEND = 'com'
$env:CDT_AUTOCAD_COM_PROGID = 'AutoCAD.Application.26'
$env:CDT_AUTOCAD_COM_ATTACH_POLICY = 'attach_only'
.\.venv\Scripts\cdt-autocad.exe --transport stdio
```
Start AutoCAD in the same interactive user/session first. `attach_only` refuses
when the application is unavailable. For headless use, install the Linux lock
where applicable and select `CDT_AUTOCAD_BACKEND=ezdxf`.
See [reproducible installation](docs/REPRODUCIBLE_BASELINE.md).
## Use safely
1. Discover `help`, `system_status` and `system_capabilities`.
2. Bind native writes to `document_pid` and `expected_parent_fp`.
3. Execute bounded semantic features, then inspect/query/measure the result.
4. Continue only after verified commit or rollback. Reconcile uncertain completion
before retrying; timeout does not prove native cancellation.
Tool presence does not imply native strong-integrity support for every route.
Configure allowed file roots; HTTP requires deployment-managed authentication.
No arbitrary shell, AutoLISP, macro or caller-supplied C# execution is exposed.
## Reference
- [Release, install and rollback](docs/RELEASE_AND_DEPLOYMENT.md).
- [Tool contract](docs/TOOL_GUIDE.md) — callable surface and guarantees.
- [Compatibility and assurance limits](docs/COMPATIBILITY.md).
- [Operations](docs/OPERATIONS_RUNBOOK.md).
- [Documentation index](docs/README.md) — architecture, security and QA references.
## License
Proprietary source-available software; public visibility grants no open-source
license. See [LICENSE](LICENSE), [copyright](COPYRIGHT.md),
[third-party notices](THIRD_PARTY_NOTICES.md) and [source provenance](SOURCE_PROVENANCE.md).
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.