FreeCAD AI plugins: what exists in 2026

I installed three different FreeCAD AI plugins last weekend. One crashed FreeCAD on launch. One worked but generated a cube when I asked for a bracket. The third, the FreeCAD AI Workbench, actually generated a recognizable bracket with mounting holes and the correct overall dimensions, then asked me if I wanted to refine it. I sat there for a moment, genuinely surprised, because the last time I'd tried AI-anything in FreeCAD, the experience was closer to reading tea leaves than engineering.

The status of FreeCAD AI plugins in 2026 is a lot like FreeCAD itself: technically capable, inconsistently polished, improving faster than you'd expect, and still not something I'd hand to a colleague without a disclaimer. Here's what exists, what works, and what's still held together with optimism and duct tape.

The FreeCAD AI Workbench#

The most developed project is ghbalf/freecad-ai, an add-on workbench that puts a chat interface directly inside FreeCAD. Currently at v0.7.0-alpha (April 2026), it connects FreeCAD to LLMs and lets you describe parts in natural language.

The feature list is ambitious for an alpha project. It has a chat panel with streaming responses, 42 structured FreeCAD operations exposed as callable tools, Plan and Act modes (Plan shows you the code before executing, Act runs it directly), support for 20+ LLM providers including Anthropic, OpenAI, Ollama, Gemini, and DeepSeek, image support so the AI can see your viewport, error self-correction with up to three retry attempts, and reusable instruction sets the developer calls "Skills" for common parts like enclosures, gears, and fastener patterns.

I tested it with Claude and GPT-4. The results were uneven but occasionally impressive. Simple prismatic parts (a plate with holes, a U-bracket, a rectangular enclosure) generated correctly more often than not. The AI created sketches on the right planes, applied Pad operations with correct dimensions, and placed features in approximately the right positions. The error self-correction is genuinely useful: when the first attempt failed (a wrong method call, a missing recompute), the plugin caught the error, sent it back to the LLM, and the second attempt usually worked.

Complex geometry was a different story. A request for a part with intersecting fillets produced an error cascade that the self-correction couldn't recover from. An enclosure with internal ribs generated the ribs as separate bodies instead of features on the main body. A request for a pattern of holes created the first hole correctly and then placed the remaining five in a line instead of a circular pattern. These aren't surprising failures. FreeCAD's Python API has patterns that even experienced scripters find unintuitive, and an LLM working through 42 tool calls to build complex geometry is going to trip over the same inconsistencies.

The Plan mode is the safer option and the one I'd recommend. It shows you the generated code before executing it, which means you can catch obvious problems before they corrupt your model. In Act mode, the AI just runs code directly, and when it goes wrong, you're left cleaning up a partially-built feature tree that might be easier to delete and restart than to fix.

FreeCAD MCP servers#

The MCP approach, connecting FreeCAD to AI assistants via the Model Context Protocol, has produced several projects.

proximile/FreeCAD-MCP offers 57 CAD operation tools, Docker-containerized headless FreeCAD execution, and vision AI analysis. The containerized approach is interesting because FreeCAD's headless mode has historically been fragile, and running it in Docker isolates the environment from your system. The 57-tool set covers sketching, Part workbench operations, measurements, and export.

Coben-3d/freecad-mcp is another MCP implementation, and several others have appeared on GitHub with varying levels of maturity. The MCP ecosystem for FreeCAD is still in the "many experiments, no standard" phase. None of these have the stability I'd want for regular use, but they demonstrate the approach.

The MCP path has one key advantage over the workbench plugin: the AI runs outside FreeCAD. If the generated code crashes, it crashes a subprocess, not your active FreeCAD session with unsaved work. The workbench plugin runs inside your live FreeCAD instance, which means a bad script can corrupt your model or crash the application. I've experienced both.

CADialogue#

CADialogue takes a different approach entirely. It's a multimodal system that accepts natural language, speech, and images as input for generating FreeCAD Python macros. The speech input means you can literally talk to your CAD tool, though in practice I find typing more precise and less likely to confuse "fillet" with "fill it."

The standout feature is macro caching: once a script has been generated for a particular operation, the system caches it and reuses it for similar requests. The developers report an 85x speedup on repeated tasks, which makes sense because LLM inference is slow and cached lookups are fast. For workflows where you're generating many variations of similar parts, this could be useful. For one-off parts, the cache doesn't help.

CADialogue also includes human-in-the-loop refinement, meaning you can approve, reject, or modify the AI's output before it executes. This is the pattern I prefer. AI generating CAD code that runs immediately without human review is a workflow I don't trust enough to use on anything I care about.

GPT4FreeCAD and older projects#

GPT4FreeCAD is an earlier project from 2023 that connects GPT-4 to FreeCAD for generating Python scripts and sketches. It's less actively maintained than the newer projects, and the FreeCAD API has evolved since it was written, but it proved the concept worked. Several of the newer projects cite it as inspiration.

FreeCAD-AI-Toolbar is another early effort, providing a toolbar interface for AI interaction within FreeCAD. The ambition was right; the execution was constrained by the LLM capabilities available at the time.

These older projects are worth mentioning because they show that the community has been trying to make this work for years. The recent improvement isn't because someone had a new idea. It's because the LLMs got better at generating correct Python, and the tool integration patterns (MCP, structured tool calling) matured enough to make the connection reliable.

Why FreeCAD is harder than OpenSCAD for AI#

The OpenSCAD + AI workflow works well partly because OpenSCAD's language is tiny and self-contained. The AI generates a text file, OpenSCAD renders it, done. There's no state management, no active session, no feature tree to corrupt.

FreeCAD is fundamentally different. It's a stateful application with a complex object model. Creating a part involves: starting a new document, creating a body, creating a sketch on a specific plane, adding geometric constraints to the sketch, closing the sketch, applying a feature (Pad, Pocket, Revolve), and calling recompute() at the right moments. Each step depends on the previous steps having completed correctly. If the AI gets step three wrong, steps four through seven produce garbage or fail.

The API surface is also much larger. FreeCAD has multiple workbenches (Part, Part Design, Sketcher, Draft, Assembly, etc.), each with its own scripting conventions. A script that works in the Part workbench might use different patterns than the same operation in Part Design. The documentation is extensive but uneven, and LLMs occasionally mix up the different workbench APIs, generating code that uses Part module functions when the context requires Part Design, or vice versa.

Constraint handling is the most consistent failure point. FreeCAD's Sketcher requires geometric constraints (coincident, tangent, perpendicular, fixed, dimensional) to fully constrain a sketch before it can be used as a feature profile. LLMs routinely generate under-constrained sketches, producing geometry that's valid but not deterministic. The sketch looks right, but it can shift unpredictably when the model recomputes. Getting an LLM to generate fully constrained sketches consistently is a problem none of these plugins has solved yet.

The honest assessment#

No mature, production-ready FreeCAD AI plugin exists in 2026. The FreeCAD AI Workbench is the closest, and it's in alpha. The MCP servers work but are unstable. The older projects are proof-of-concept quality.

That said, the trajectory is clearly upward. The FreeCAD AI Workbench went from initial release to v0.7.0 in a few months, adding structured tool calling, vision support, error correction, and multi-provider support at a pace that suggests active, sustained development. The MCP ecosystem is growing. The LLMs themselves keep getting better at Python, which directly improves FreeCAD script quality.

If you want to try AI-assisted FreeCAD today, start with the FreeCAD AI Workbench in Plan mode. Use a capable model (Claude or GPT-4). Keep your requests simple. Save your work before letting the AI execute anything. And expect to read and fix the generated code, because the plugin is a starting point, not a finished product.

For simpler parts that don't need STEP export or assembly features, the OpenSCAD path is more reliable today. For parts that need FreeCAD's full capabilities, AI-generated macros with manual review and editing remain the most practical approach. The plugins are getting there. They aren't there yet. If FreeCAD's history is any guide, they'll arrive eventually, slightly later than hoped, and with at least one dependency that requires building from source.