OpenSCAD MCP Server

Render STL and PNG from OpenSCAD code. The openscad mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.

What it actually does

An MCP (Model Context Protocol) server that renders PNG previews and STL geometry from OpenSCAD (SCAD) source code. It is designed to support iterative, agent-driven CAD workflows, where models can be previewed visually and exported for downstream use (e.g. fabrication, simulation, or inspection).

Adding it to your client

skills on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

• render_scad_png — Renders a PNG preview image from SCAD source
• Input — scadCode (string), optional width/height (numbers), optional cameraPreset and optional cameraPosition
• cameraPreset — one of isometric, front, back, left, right, top, bottom
• cameraPosition — { x, y, z }
• Output — MCP ImageContent
• export_scad_stl — Exports an STL generated from SCAD source

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the openscad mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. OpenSCAD's toolset — render_scad_png, Input, cameraPreset and 3 more — is a fair guide to whether it matches your workflow. It is maintained by fboldo; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.