CADCraft Gives AI Agents Full AutoCAD 2D Drafting Control at Zero Licensing Cost

A new open-source project called CADCraft shipped on October 8, 2026, and within four days had accumulated more than 3,000 GitHub stars — a reception that reflects both pent-up demand for a no-subscription AutoCAD alternative and growing developer interest in CAD tools that AI agents can actually control. Built entirely in Rust by the ArtCraft development team, CADCraft is a clean-room reimplementation of the AutoCAD 2D drafting workflow, dual-licensed under MIT and Apache 2.0, and available at no cost across macOS, Windows, Linux, FreeBSD, and the browser via WebAssembly. It ships with a built-in MCP (Model Context Protocol) server, which means any compatible AI agent can issue drafting commands, query drawing contents, and export geometry directly — without a human CAD operator in the loop.

The immediate question for anyone who has paid AutoCAD's subscription invoices is straightforward: does it actually work with professional drawings? The answer that emerges from the project's documentation and early community testing is cautiously yes, with the meaningful qualifier that v0.1.0 is a first release and that real-world DWG round-trip reliability still needs broader validation.

The $0 vs. $2,095 Calculation That Drives This Conversation

Autodesk moved AutoCAD to a subscription-only model in 2021, and the current pricing for AutoCAD 2026 runs roughly $260 per month or $2,095 per year depending on plan and region. For individual consultants, small architecture firms, or hobbyists who used to buy a perpetual license and amortize it over years, that arithmetic no longer works. It also creates a meaningful cost constraint for AI infrastructure engineers who want to build agent pipelines that generate or modify technical drawings at scale — each drawing operation would implicitly carry a per-seat license cost.

CADCraft's response to that situation is structural rather than incremental. The project is not a reduced-feature preview or a viewer with limited export. According to its documentation and README, it implements the full AutoCAD 2D command interface: LINE, CIRCLE, OFFSET, TRIM, EXTEND, HATCH, BLOCK, INSERT, the DIMSTYLE variable system with associative dimensions, paper space with viewports, PLOT, and EXPORTPDF. Whether every one of those commands performs identically to AutoCAD in edge cases is an open empirical question — but the scope of what the team is claiming is the full professional drafting surface, not a curated subset.

Under the Hood: Rust, egui, and GPU-Accelerated Rendering

The technical choices behind CADCraft address some of the chronic complaints about earlier open-source CAD tools. FreeCAD, LibreCAD, and QCAD are all written in C++ and rely on Qt for their graphical interfaces — a combination that has historically produced inconsistent behavior across platforms, non-trivial packaging overhead, and performance that degrades on large drawings.

CADCraft's UI layer is built on egui, a Rust-native immediate-mode GUI framework. Immediate-mode design means the application rebuilds its interface state every frame rather than maintaining a persistent widget tree. For a command-driven application where the canonical interaction is a short text command followed by a visual response, this architecture is a natural fit: state is explicit, transitions are predictable, and the interface compiles to both native binaries and WebAssembly without a separate rendering path.

The rendering backend is wgpu, a Rust-native GPU abstraction that targets DirectX 12 on Windows, Vulkan on Linux, Metal on macOS, and WebGPU in browsers. This matters practically because it means the same rendering code produces hardware-accelerated output on all platforms without OpenGL's well-documented driver variability. Older open-source CAD tools that use OpenGL 2.x compatibility profiles have persistent issues with Intel integrated graphics and modern Wayland compositors; wgpu's modern API targets resolve most of those.

The project ships as a single self-contained binary on every supported platform — no Electron, no Qt installation, no system library dependencies beyond the graphics driver. Windows users get an MSI installer or a portable zip in x64, ARM64, and x86 variants. macOS gets a universal DMG that is both signed and notarized. Linux packaging includes AppImage, Flatpak, deb, rpm, and tar.gz, with builds for x86_64, aarch64, and riscv64, all available from the project's releases page. The WebAssembly build deploys as a static site with no server-side component.

DWG Support Changes the Open-Source CAD Calculus

For professional use, the capability that separates a functional AutoCAD alternative from a technically interesting experiment is DWG file compatibility. AutoCAD's binary DWG format is the de facto interchange format for the architecture, engineering, and construction industries. A CAD tool that cannot open or save DWG files is effectively a parallel universe — useful for drawing new documents but disconnected from the existing file ecosystems that architects and engineers actually operate in.

CADCraft handles DXF — AutoCAD's documented ASCII and binary interchange format — natively, across all versions from R12 through the current 2018 specification, with output written as R2000-format DXF. This alone would make it a credible DXF-to-SVG or DXF-to-PDF conversion tool.

The DWG support is a separate matter. CADCraft reads and writes DWG files through acadrust, an open-source Rust library for the DWG and DXF formats. DWG is Autodesk's proprietary binary specification; no official open documentation exists, and the Open Design Alliance has historically pursued legal action against open-source implementations. acadrust — like LibreOffice's DWG import — operates in the same legal territory as Wine or ReactOS: technically functional, legally uncertain, widely used in practice. The practical question for a professional firm is whether acadrust's R13-through-2018 DWG implementation handles their specific drawing library reliably. At four days post-release, that question can only be answered through accumulated user testing.

LibreCAD, the most comparable 2D-only open-source tool, does not support DWG natively. QCAD offers DWG support as a paid plugin. FreeCAD's primary design surface is 3D parametric modeling with a Python scripting environment — it handles DXF for simple cases but is not a 2D drafting environment in the AutoCAD sense. The practical gap CADCraft fills is the one that has made FreeCAD and LibreCAD only partial substitutes for AutoCAD in professional contexts.

Every Command Is an Agent Call: The MCP Architecture

The feature that separates CADCraft from every other open-source CAD tool is architectural rather than functional: every user-facing drafting command is simultaneously an agent-callable MCP tool.

This design works because CADCraft's interface is command-first. When a user opens the layer manager, changes a dimension style, or draws a hatch boundary, that action is internally represented as a named command with parameters — the same command the user could have typed. The application does not maintain a separate scripting layer or a plugin API distinct from the user interface. The command surface is the interface.

The MCP server that ships with CADCraft (launched via cadcraft-cli mcp) exposes that entire command surface to AI agents through a standardized JSON-RPC protocol. The documented tool calls include command_line for sending text commands as a user would type them, execute for structured JSON-parameterized command calls, inspect_drawing for retrieving structured data about drawing contents, query_entities for filtering entities by layer or type, render for receiving a PNG rendering of the current drawing state directly as a response payload, and screenshot for capturing the current UI state.

The presence of AGENTS.md and CLAUDE.md in the repository root — documents that describe expected AI agent behavior within the project — confirms that agent-first development was a design goal rather than a post-release addition. The render tool is particularly significant: it allows an agent to receive visual feedback on a drawing state without needing external screenshot infrastructure, completing a closed perception-action loop entirely within the MCP protocol.

The command-line interface, cadcraft-cli, enables the same workflow non-interactively:

cadcraft-cli run --sample --script 'CIRCLE 22,3 1\n' --save out.dxf --export out.png
cadcraft-cli convert drawing.dxf drawing.svg
cadcraft-cli mcp

This makes headless CAD operations — batch DXF-to-PDF conversion, AI-generated drawing export, format migration pipelines — usable without a display server and without an interactive session. For infrastructure engineers building agent pipelines, the practical consequence is that CADCraft can be deployed in a container, controlled over MCP, and produce DXF, SVG, PNG, or PDF output without licensing overhead.

The closest comparable tool in the Rust ecosystem is vcad (ecto/vcad on GitHub), which also implements an MCP server for CAD operations. However, vcad targets 3D boundary representation (BRep) parametric modeling rather than 2D drafting — it is not a replacement for AutoCAD's drafting workflow. Open CAD Studio is another Rust-based 2D CAD project using iced and wgpu, but it lacks DWG support and does not expose an agent interface. CADCraft is currently the only open-source 2D drafting tool that combines AutoCAD command-line UX parity, native DXF, DWG read/write, and a native MCP server.

Where CADCraft Sits in the Open-Source CAD Field

The open-source CAD ecosystem has historically split into two categories: tools that match AutoCAD's feature depth but not its professional interoperability (FreeCAD, BRL-CAD), and tools that approximate AutoCAD's 2D workflow but lack the file format support needed for professional exchange (LibreCAD). CADCraft's positioning addresses the second gap directly.

FreeCAD is a capable parametric 3D modeler with a substantial user community and Python scripting. Its 2D drafting mode (the Draft workbench) is functional but not designed around the AutoCAD command-line muscle memory that 2D drafting professionals use. FreeCAD does not support DWG natively; opening DWG files requires the FreeCAD-provided DXF library or an ODA File Converter, neither of which integrates transparently. FreeCAD has no MCP interface.

LibreCAD focuses specifically on 2D drafting and is the closest analog to CADCraft in functional scope. It implements a command line and most AutoCAD 2D primitives. It does not support DWG. It does not have a programmatic agent interface. Development has been active but not fast-moving.

AutoCAD itself has introduced AI features through Autodesk's AI initiative, but these are copilot-style assistants layered onto the application — the user remains the operator, and the AI makes suggestions. CADCraft's approach is structurally different: the AI agent is the operator, and the CAD engine is the tool being called.

CADCraft's clean-room reimplementation claim means the project was built from observed behavior and documented specifications rather than from AutoCAD's source code. The legal precedents for this approach are well-established (Wine, ReactOS, OpenJDK), though Autodesk's track record on enforcing its IP around the AutoCAD command interface is less extensively tested than Microsoft's response to Wine.

What v0.1.0 Does Not Yet Settle

A first release in a category this complex leaves meaningful questions open.

The most important practical unknown is DWG fidelity at scale. acadrust's R13–2018 DWG support has not yet been tested across the range of drawing complexity that production architecture or mechanical engineering firms produce. Complex DWG files with external references (XREFs), proprietary entity types, or advanced annotation styles may expose compatibility gaps. Community-contributed testing over the next few months will determine whether CADCraft can genuinely substitute for a licensed AutoCAD or DWG-compatible tool in file-exchange workflows.

The MCP server's reliability under concurrent agent calls and long-running agent sessions is also unvalidated at this stage. An agent running a multi-step drawing pipeline — read a DWG, extract room boundaries, add dimensions, export to PDF — will exercise the MCP implementation in ways that short demo scripts do not. Failure modes in agent tool calls (timeouts, incomplete entity queries, rendering artifacts) will become visible only through broader deployment.

CADCraft does not implement AutoLISP or any equivalent macro scripting language, which means AutoCAD users who have invested in custom LISP routines cannot migrate those workflows directly. The MCP approach is architecturally better suited to AI-native workflows than to traditional scripting, but it requires rethinking the automation layer for existing LISP-dependent workflows.

The ArtCraft organization behind the project maintains a suite of professional applications including PhotoCraft, VectorCraft, FilmCraft, and others, suggesting ongoing institutional support — but the organizational structure is not publicly documented, and the long-term sustainability of a no-subscription, MIT-licensed professional CAD tool depends on community contribution and developer continuity in ways that proprietary tools do not.

What is clear at this stage is that CADCraft has set a new functional baseline for open-source 2D CAD: AutoCAD-habit command parity, native DXF and DWG, GPU-accelerated rendering without framework overhead, and a complete AI agent interface built into the same binary. For the broader question of whether professional-grade design tooling can be delivered to AI agents without a per-seat licensing model, CADCraft's architecture provides the first serious affirmative evidence. The next test is whether the community can validate its DWG fidelity at the scale the professional drafting world demands.

CADCraft is available at github.com/storytold/cadcraft under MIT OR Apache-2.0 license. The project requires Rust 1.95 or higher to build from source.