openscad-mcp-server
Related Servers
Alternatives to openscad-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to render 3D models by providing tools to execute OpenSCAD code and generate single or multi-perspective views. It returns high-quality PNG renderings directly to LLM applications for visual feedback and 3D model visualization.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to create and manipulate 3D CAD models using OpenSCAD.410 npm1MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to render 3D models from OpenSCAD code, generating single views or multiple perspectives with full camera control. Supports animations, custom parameters, and returns base64-encoded PNG images for seamless integration.12203 PyPI149MIT
- AlicenseNot gradedqualityDmaintenanceEnables agents to validate, render preview (PNG), and export OpenSCAD models to various formats using the openscad CLI.139 npmMIT
- AlicenseNot gradedqualityCmaintenanceExposes OpenSCAD CLI as MCP tools for validating, rendering, and exporting parametric 3D models. Enables LLM clients to interactively create and manipulate OpenSCAD designs.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to create and manipulate 3D models using OpenSCAD through MCP tools for code-based modeling, preview, and export.1MIT
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.