SolidCraft makes the control path explicit.
SolidCraft 0.7.0 is an early parametric CAD application written in Rust. It has constrained sketches, a feature timeline, parameters, assemblies, import and export routes, a desktop interface, a browser build, a command-line tool, and an MCP server. The project says it is usable for simple parts and lists known geometry limits beside that claim.[1][2]
The useful architectural choice is one command registry behind the interfaces. The documented script format calls operations such as sketch.create, sketch.rectangle.two_point, and solid.extrude. The MCP server exposes command discovery, execution, batch work, design inspection, measurement, parameter changes, screenshots, exports, undo, redo, open, and save.[1]
The shared command is the beginning of reproducibility. It is not the finished proof.
Parametric CAD carries hidden state.
A final mesh can look right while the editable model is wrong. A dimension may be hard-coded. A sketch may be attached to the wrong face. A feature can rebuild against a different reference after an upstream edit. An export can flatten the history that made the part adjustable.
SolidCraft's own release notes show this problem in concrete form. Version 0.7.0 changes the design-file format. It also fixes sketching on stacked extrudes, feature rename references, shell and fillet cases, and STEP output for multi-lump bodies. The release still names face-attachment and geometry failures that need work.[2]
This is not an argument against agent-driven CAD. It is a reason to review the model as a sequence. The reviewer needs the source revision, design-file format, command list, rebuild result, measurements, and export digest.
Measure after the rebuild.
The repository reports that 75 of 76 public reference parts match analytic or FreeCAD-computed volume, area, center of mass, and bounding box values. It also says those checks do not prove complete geometry or workflow equivalence.[1]
That caveat is the right shape. A useful acceptance record can compare volume, area, bounding box, face count, named parameters, and one rendered view. The required checks depend on the part. A mounting bracket may need hole spacing and thickness. A sealed enclosure may need wall thickness, interference clearance, and a successful section view.
DESIGN_REVISION=a9879fa
DESIGN_FORMAT=solidcraft/15
COMMAND_LOG=[REQUIRED]
REBUILD_RESULT=[REQUIRED]
PARAMETERS=width,height,hole_spacing
MEASUREMENTS=volume,bounds,center_of_mass
EXPORT_FORMAT=STEP_AP242
EXPORT_SHA256=[REQUIRED]
REVIEWER=[REQUIRED]MCP exposes tools. The host owns the review.
The current MCP architecture lets a host discover and call server tools. Tool results can contain text, images, or structured data. The protocol defines the exchange, while the host decides how tools enter the model's context and how a person reviews actions.[4]
For CAD, that means execute and export should not collapse into one vague success state. Command acceptance, model rebuild, geometric inspection, and file creation are separate events. The interface should show each one.
The Truck modeling crate supplies integrated geometry and topology algorithms used at SolidCraft's kernel boundary. Its documentation identifies building, geometry, topology, and sweep utilities. That dependency record helps locate the geometry layer. It does not prove a given model operation is correct.[3]
Keep the editable source beside the export.
STEP or STL is a delivery artifact. The parametric design is the repair path. Keep both when a model matters. Save the command record too, because it explains how the design changed and lets another operator replay the intent against a later build.
The minimum handoff is small. Pin the application revision. Save the editable design. Record the commands. Rebuild from a clean open. Measure the properties that can reject a bad part. Export once. Hash the export. Then let a person sign the result.