VibeCAD (wangtao9090)
FreeCAD expert agent for host agents such as Claude, Codex, and WorkBuddy, with a 39-tool MCP and skill contract and a managed FreeCAD runtime.
Summary rewritten from the vendor site because the catalog version did not match it.
What it does and how it connects
VibeCAD is a FreeCAD expert agent for host agents such as Claude, Codex, and WorkBuddy. It turns design intent into persistent projects, constrained CAD operations, reviewable drafts, and verified FCStd and STEP resources. It neither embeds nor resells a large language model: reasoning uses the user's own host model and its subscription or API quota.
The tool exposes a host-neutral 39-tool MCP and skill contract, and ships a FreeCAD Workbench Alpha for project and task discovery, HEAD and draft preview, verdict, Accept, and Reject. Execution runs through a deterministic task kernel with isolated candidates, an explicit review policy, verified artifacts, recovery, and replay-safe request semantics.
VibeCAD manages its own FreeCAD runtime, so users do not need to prepare a compatible system FreeCAD. The supported paths are Windows x86-64 and macOS, and the first launch downloads about 2 to 3 GB of locked runtime files. Designs are editable and parametric, with bounded derived-parameter linkage and semantic fillet and chamfer treatments.
Alternatives
Compare side by side- VibeCAD (rawwerks)
A library of Claude Code skills across several CAD tools, while VibeCAD is a FreeCAD-specific MCP server and workbench.
- text-to-cad
Generates CAD from text prompts through coding agents, while VibeCAD is a FreeCAD expert agent with a 39-tool MCP contract.
- build123d
A Python code-first CAD library, while VibeCAD drives FreeCAD through an MCP server with a managed runtime.
- chili3d
A browser CAD application, while VibeCAD is an agent layer on top of FreeCAD with a review workbench.
- SolidCraft
A desktop CAD program with an MCP server, while VibeCAD is a FreeCAD expert agent with its own managed FreeCAD runtime.
Recurring errors it addresses
Error Index entries this tool is built to reduce or work around.
- When an agent fans out parallel create calls through the FreeCAD MCP bridge, the shared connection races: the first object is created even though its call reports failure, and the second object is silently never created with the status still showing healthy.Error Index
- A FreeCAD MCP bridge silently ignored parameters the client materialized from JSON-Schema defaults, so box(size=20) produced a default 10mm shape. The agent believes it built the requested geometry while the model is something else entirely.Error Index
- A FreeCAD MCP bridge's autosave-before-call rewrote the active document on every tool call even with zero unsaved changes, stamping phantom diffs onto git-tracked CAD files. Agent activity pollutes version control with edits no human authored.Error Index
- A FreeCAD MCP bridge's persistent execution namespace meant that once any call bound a variable named result, every later call echoed the old value as its own output. The agent reads that output and believes its code produced a value it never computed.Error Index
- A FreeCAD MCP bridge reported clean instance shutdowns as failures 100 percent of the time on Linux, because its liveness check polled immediately after signaling the process group. The agent was sent to retry or kill processes that were already gone.Error Index
Sources
Not verified
- Pricing (none stated on the repo; reasoning uses the user's own host model subscription or API quota)
- Real user voices (the only open items are maintainer pull requests)
- A named individual builder beyond the repository owner handle wangtao9090
Last verified November 6, 2026. Listings are informational. The evidence score measures public, verifiable evidence and is not an endorsement or a compatibility claim.