SolidCraft vs FreeCAD

SolidCraft facts from the tangency-labs/solidcraft README, docs.solidcraft.io, and ROADMAP (tracked release here: v0.16.2). FreeCAD facts from freecad.org, License docs, third-party libraries, and the FreeCAD 1.1.4 release notes. FreeCAD® is a trademark of its owners; this site is unaffiliated with the FreeCAD project and Tangency Labs.

Community orientation guide — not a lab benchmark. Prefer primary docs when versions disagree.

SolidCraft web app showing the official Sample Plate with feature timeline visible — SolidCraft web app (v0.16.2) — Sample Plate with parametric timeline. Reused from this site’s example assets.

At a glance

Topic	SolidCraft	FreeCAD
License	MIT OR Apache-2.0 (dual)	LGPL-2.0-or-later (application)
Geometry kernel	Pure-Rust B-rep stack (SolidCore / project kernel work)	OpenCASCADE Technology (OCCT)
UI model	Single parametric editor + feature timeline	Workbench-based (PartDesign, Sketcher, TechDraw, Path, FEM, …)
Sketch constraints	Constrained sketches on the timeline	Sketcher workbench (mature constraint solver)
Maturity	Early; “usable for simple parts” per project	Mature 1.x line (1.1.4 maintenance as of 2026-09)
Drawings / CAM / FEM	Deferred on official roadmap	TechDraw, Path (CAM), FEM workbenches
Native format	`.solidcraft`	`.FCStd`
Interchange	STEP, IGES, 3MF, STL, OBJ; `.FCStd`/Rhino via cadmpeg	STEP, IGES, STL, SVG, DXF, OBJ, IFC, DAE, and more
Fusion `.f3d`	No native importer documented — use STEP	No first-party Fusion native importer (use STEP/interchange)
Platforms	Windows / macOS / Linux desktop + official wasm web app	Windows / macOS / Linux desktop (primary)
Scripting	JSON command scripts, headless CLI, unit-aware parameters	Deep Python API, macros, workbench addons
AI / MCP	Built-in `solidcraft-cli mcp`	Community MCP bridges (e.g. freecad-mcp); not core

Kernels and modelling style

SolidCraft models solids with a pure-Rust B-rep approach and an editable feature timeline (sketch → extrude/fillet/shell/… → change a parameter and rebuild). The project also develops SolidCore as a Rust geometry kernel effort.

FreeCAD builds on OpenCASCADE (OCCT), a long-standing C++ CAD kernel, and exposes modelling through specialized workbenches. That modularity is FreeCAD’s strength for drawings, CAM, FEM, and BIM-oriented tasks.

Who should pick which

Prefer SolidCraft when…

You want an agent-native CAD loop (MCP/CLI) without standing up a separate FreeCAD bridge.
Parts are relatively simple parametric solids / enclosures matching the project’s early scope.
You care about a browser app plus desktop, or dual MIT/Apache licensing for embedding experiments.

Prefer FreeCAD when…

You need TechDraw drawings, Path/CAM, FEM, or BIM-oriented workbenches today.
You already live in FreeCAD’s Python/macro/addon ecosystem.
You want a larger, longer-running open-source CAD community and training materials.

SolidCraft web UI showing the official parametric bracket example — Official `examples/bracket.json` opened in the SolidCraft web app — typical simple-part scope.

File formats and migration

Best shared solid format: STEP (both directions).
FreeCAD → SolidCraft: STEP, or .FCStd via cadmpeg (geometry import; history not preserved).
SolidCraft → FreeCAD: export STEP/IGES/mesh as needed, then continue in FreeCAD workbenches.
Fusion .f3d: neither project documents a faithful native Fusion history importer; export STEP from Fusion first.

FAQ

Is SolidCraft a FreeCAD replacement?

Not today for most production workflows. FreeCAD (latest stable 1.1.x) is a mature, workbench-based suite with TechDraw, Path/CAM, FEM and a huge addon ecosystem. SolidCraft is early, focused on parametric solids, a single editor workflow, and first-class MCP/CLI automation.

Can SolidCraft open FreeCAD .FCStd files?

Yes for solids via the documented cadmpeg path (same family as STEP import): you get geometry as an Import base feature, not FreeCAD’s full parametric history. Prefer STEP when you only need B-rep interchange.

Does FreeCAD have MCP like SolidCraft?

SolidCraft ships solidcraft-cli mcp in-tree. FreeCAD MCP exists as community projects (for example neka-nat/freecad-mcp) that typically require FreeCAD running with an addon or bridge—not a built-in stdio server in the core app.

Which is better for AI agents?

If you want a local, headless CAD command surface with one binary, SolidCraft’s MCP is designed for that. FreeCAD agents usually drive FreeCAD through community MCP bridges and Python. Pick based on whether you need FreeCAD’s workbenches or SolidCraft’s agent-native CLI.

What about drawings, CAM, and FEM?

FreeCAD includes TechDraw, Path (CAM), and FEM workbenches. SolidCraft’s public roadmap defers drawings, CAM/manufacture, and simulation.

Sources

SolidCraft README / docs / ROADMAP — https://github.com/tangency-labs/solidcraft, https://docs.solidcraft.io/
FreeCAD project site — freecad.org
FreeCAD license — License.md
FreeCAD / OCCT — Third_Party_Libraries.md
FreeCAD 1.1.4 release — GitHub Releases
Community FreeCAD MCP — neka-nat/freecad-mcp