formastep-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORMASTEP_WORKSPACE_ROOT | No | Confines all file reads and artifact writes to a specific directory. Defaults to the current working directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Headless parametric 3D CAD engine: compile PartSpec JSON, inspect ISO 10303-21 STEP files, run DFM manufacturability audits, and render orthographic SVG drawings.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| part_buildC | Compile a parametric PartSpec JSON dict and export STEP/3MF/STL/SVG artifacts. |
| step_inspectB | Inspect and validate an ISO 10303-21 STEP (.step/.stp) file. |
| dfm_auditC | Run DFM QA checks (watertightness, wall thickness, overhangs, BOM) on a PartSpec or mesh file. |
| view_render_svgB | Render a deterministic 3-view orthographic SVG (Top/Front/Right) from a PartSpec or mesh. |
| export_manufacturing_bundleB | Compile PartSpec, validate STEP + DFM, and export a full manufacturing bundle with SHA-256 manifest. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
part_build and export_manufacturing_bundle substantially overlap, since both compile a PartSpec and export artifacts, with the bundle tool just chaining validation and DFM on top. step_inspect and dfm_audit also both perform validation-style checks, making the boundary between 'inspect' and 'audit' unclear. The descriptions help somewhat, but an agent could plausibly pick the wrong one for a simple export request.
All names are snake_case, but the word order convention is mixed: part_build, step_inspect, and dfm_audit lead with a noun, while view_render_svg and export_manufacturing_bundle lead with a verb. Readable individually, but there is no predictable pattern an agent can rely on to guess a tool name.
Five tools is a tight, well-scoped set for a parametric CAD pipeline covering build, inspect, audit, render, and package. It is on the lean side, with the bundle tool arguably absorbing part_build's role, but nothing feels gratuitous.
The surface covers the core lifecycle: author a PartSpec, validate the resulting STEP, run DFM checks, visualize, and export a manifest bundle. Gaps exist around editing or mutating an existing PartSpec and around converting an existing STEP/mesh back into a PartSpec, which an agent might reasonably expect.