Automation and AI
Drive 3DsWorks from commands, the CLI, MCP tools and the built-in assistant.
Everything is a command
Every action in the interface maps to a command, and every command can be called from the command search, the CLI, the local control channel or an MCP client. That is what makes 3DsWorks scriptable without a plugin API.
Press S and type a command id with a JSON object to run it with explicit values:
solid.extrude {"distance": 20}
The popup validates the JSON as you type. Enter runs it; Shift+Enter runs it and keeps the popup open.
CLI
solidcraft-cli runs commands without opening a window:
solidcraft-cli commands— the command catalogue as JSON.solidcraft-cli run script.json --out part.step— replay a list of commands.solidcraft-cli eval design.sc— volume, area, bounding box and other measures.solidcraft-cli snapshot design.sc --out part.png --view iso— a picture from a standard or saved view.solidcraft-cli script design.sc --out repro.json— a design's history as a rebuildable script.
A script is a command list:
{"commands": [{"command": "sketch.create", "params": {"plane": "XY"}}, {"command": "sketch.rectangle.two_point", "params": {"p0": [0,0], "p1": [40,30]}}, {"command": "sketch.finish", "params": {}}, {"command": "solid.extrude", "params": {"distance": 20}}]}
--results prints each command's result, --timings prints how long each step took, and --allow-errors keeps writing output when a feature fails.
MCP
solidcraft-cli mcp starts a Model Context Protocol server. Point an MCP client at it, or use the assistant inside 3DsWorks. The tools cover the session, the model and the checks:
| Tool | What it does |
|---|---|
execute | Run one command. |
batch | Run several commands as one all-or-nothing step. |
measure | Volume, area, bounding box, centre of mass, face count. |
inspect_design | Timeline features, warnings, parameters and studies. |
screenshot | A model view or the whole window, as a PNG. |
export / save | STEP, 3MF, STL, OBJ, URDF, or a .sc design. |
open | Open an existing design. |
drawing | Build a whole 2D sheet in one call, with optional SVG or DXF. |
The server also serves the bundled modelling skills for skill_reference, so an agent can read the same conventions this manual describes.
The assistant
The Assistant panel in the window connects to a model and can build or change the design through commands. It shows the model already selected and the files it is allowed to touch. Changes land as normal editable features on the timeline.
- Cloud models: choose a provider and model in the assistant's model list.
- Local models: point the assistant at an Ollama or OpenAI-compatible endpoint. Local endpoints keep design data on your network.
- Context: attach the current selection, a body or the whole design when the request needs it.
Permissions and files
MCP and assistant file access is limited to the allowed folders: the design's own folder, the recovery folder, the scratch folder and any path explicitly allowed at launch. Paths are resolved before they are compared, so .. and links that leave the allowed set are refused.
A programmatic call never opens a dialog. If a command needs a choice that a dialog would ask for, it takes the value as a parameter instead.
Working with an agent
- State the part as numbers first: parameters, placement, expected volume and bounding box.
- Build in a few large batches, and check each stage with a measurement.
- Put a risky step in a batch of its own so a failure does not roll back work around it.
- A success reply is not a check. Compare a measurement with a value you computed.
open or new_design when the current design has unsaved changes.