openscad-mcp-server

Export OpenSCAD source to an STL

export_scad_stl

Converts OpenSCAD source code into an STL file and returns it as an embedded resource blob for CAD workflows.

Instructions

Export OpenSCAD (SCAD) source code into an STL and return it as an embedded resource blob.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filename`	No	The name of the output STL file
`scadCode`	Yes	The OpenSCAD code to render

Output Schema

TableJSON Schema

Name	Required	Description	Default
`type`	Yes
`_meta`	No
`resource`	Yes
`annotations`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.6Sep 27, 2026

changedOutput schema / properties / annotations / properties / lastModified / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"

First observedv0.0.0Aug 11, 2026

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It does disclose the return transport ('embedded resource blob'), but says nothing about render failure modes for invalid SCAD, expected runtime/cost, or how the resource is referenced. That leaves significant gaps for a rendering tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that states the transform, the target format, and the return mechanism with zero filler. Nothing is padded or repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the tool is simple with only two params. However, the description omits any failure behavior and any routing guidance relative to render_scad_png, leaving it adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters (scadCode, filename) are already documented in the schema. The description adds no additional parameter meaning beyond what the schema provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource: exporting SCAD source into an STL, plus the key detail that it returns an embedded resource blob. It is clearly distinct from the sibling render_scad_png in what it produces, but it never names the sibling, so the differentiation relies on the agent inferring STL-vs-PNG.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of the sibling render_scad_png. An agent must infer from 'STL' that this is for 3D mesh output rather than a raster image, so the usage boundary between the two tools is left unstated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server