openscad-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for HTTP mode (default: 3000). Not required for stdio mode. | 3000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| render_scad_pngA | Render OpenSCAD (SCAD) source code into a PNG preview image. Provide the SCAD text in |
| export_scad_stlB | Export OpenSCAD (SCAD) source code into an STL and return it as an embedded resource blob. |
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 2 tools
The two tools target clearly different outputs: render_scad_png produces a raster preview image, while export_scad_stl produces a mesh file blob. An agent can trivially tell which to call based on whether it wants a preview or a downloadable geometry file.
Both names follow a strict verb_noun_object pattern (render_scad_png, export_scad_stl), using snake_case with the source format and target artifact made explicit. The convention is predictable and self-documenting.
At two tools the surface is on the thin side, though the server's scope (turning SCAD source into viewable/exportable artifacts) is narrow enough that this is defensible. Each tool clearly earns its place, but there's little room for variation in workflow.
The core lifecycle—preview and export—is fully covered, and the render tool even exposes camera controls. Minor gaps remain: no alternative export formats (3MF, SVG, DXF, OFF) and no way to validate or inspect SCAD code without producing an artifact.