CAD Agent Foundation MCP server

CAD Agent Foundation — AutoCAD MCP & CLI for AI Agents

Public source preview v1.1.0-rc.1 (bounded native operations and Windows runtime preview). Source, documentation and a manifest-bearing Windows runtime ZIP are provided in this preview. Build prerequisites and limits. The accepted local runtime v1.0.0-local is a separate baseline. Companion Skill previews are published independently: callout v0.3.0-rc.1 and distress v0.1.0-rc.1.

简体中文 · Quick start · Capabilities · Compatibility

Registered MCP server: io.github.capskov/cad-agent-foundation. MCPB installation and discovery · Registry metadata. Local Windows/AutoCAD prerequisites still apply; registration does not grant drawing access.

AutoCAD automation bridge for AI agents via MCP and CLI, using a native .NET API.

AI agents can inspect and operate a live AutoCAD drawing through structured native tools for bounded 2D geometry, text, hatches and callouts. The bridge uses MCP (Model Context Protocol) and CLI; drawing identity checks and write/save verification govern the supported operations.

CAD Agent Foundation gives CAD agents a bounded execution contract: explicitly bind a drawing, persist request ownership and execution state, inspect the original request after an uncertain reply, and verify tracked object facts after writes and saves. The current implementation integrates these mechanisms into a modified, pinned Bimwright DWG MCP host.

This Windows/AutoCAD bridge is maintained by capskov. The current preview is v1.1.0-rc.1, with an independently built runtime ZIP and scoped native evidence. The accepted v1.0.0-local baseline is retained; compatibility with every AutoCAD update is not claimed.

Why this project exists

The project grew out of road and civil-engineering CAD work: creating boundaries, fills, quantities and linked callouts, then revising and saving them over a long agent session. A useful drawing command is only part of that workflow. The agent also needs to know which drawing it owns, whether a modification has already happened, what remains unverified, and whether another attempt would duplicate it.

The design focuses on those decisions. Durable records, drawing identity and native readback add overhead; no comparative speed, token-cost or productivity advantage has been established. Engineering judgment and domain-specific layout rules remain in separate Skills.

Native operations and installation

Download v1.1.0-rc.1 runtime, verify SHA256SUMS.txt and extract the complete folder. Requires licensed compatible Windows x64 AutoCAD 2026, .NET 8 Desktop Runtime and Python 3.11+. No Autodesk assemblies or SHX fonts are redistributed. Installation · 25-operation catalog · New validation.

New in this preview: installed-font text styles, dimension styles, native linear/aligned/radius/diameter DIMENSION, layer state management, guarded closed-boundary/hatch continuation, linked callout geometry/format, and same-drawing rotate/scale/copy of supported complete groups. It preserves original-request reconciliation and drawing/object protection.

Current capability overview

Maturity: the bounded local runtime has native acceptance evidence; The release provides a runtime ZIP with dependency licenses, file hashes and plugin MVID; prerequisites remain separately installed. Support follows the actually exposed profile.

Shortened. The full README is on GitHub.