3DsWorks
Menu
Docs / Automation and AI

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:

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:

ToolWhat it does
executeRun one command.
batchRun several commands as one all-or-nothing step.
measureVolume, area, bounding box, centre of mass, face count.
inspect_designTimeline features, warnings, parameters and studies.
screenshotA model view or the whole window, as a PNG.
export / saveSTEP, 3MF, STL, OBJ, URDF, or a .sc design.
openOpen an existing design.
drawingBuild 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.

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

Safety: opening or creating a design discards unsaved work. In a bridged session, ask before open or new_design when the current design has unsaved changes.