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_stlA | 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
Each tool produces a distinct output format: PNG preview versus STL export. No overlap in purpose, and both descriptions clearly specify their output.
Both tools follow a consistent verb_noun pattern: render_scad_png and export_scad_stl. The naming clearly indicates the action and target format.
At 2 tools, the server is minimal but covers basic rendering/exporting needs. It is slightly thin but not unreasonable for a narrowly scoped utility.
The server provides a render and an export operation, but lacks common auxiliary functionality such as error checking, previewing in 3D, or accessing model metadata. The core workflow of generating a preview and exporting an STL is covered.