scad-mcp
Related Servers
Alternatives to scad-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceCreate and edit parametric 3D models with OpenSCAD. Render STL meshes and PNG previews, export SCAD, STL, CSG, and 3MF, and persist model revisions through MCP over stdio or local HTTP. Includes headless Docker support; no GPU or API keys required.8215MIT
- AlicenseAqualityBmaintenanceEnables generating parametric 3D-printable parts from OpenSCAD/CadQuery models, exporting STL/3MF files, running DFM checks, and retrieving Bambu X1 Carbon starting profile notes.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and read a self-hosted 3D model library, including G-code revisions, slicer settings, previews, print history and statistics, while also updating tags, descriptions, revision status, logged prints, and imports without delete tools.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-driven 3D model generation and manipulation using OpenSCAD through natural language commands. Users can create primitives, apply transformations, perform boolean operations, and export models to various formats like STL and OBJ.6 npmMIT
- AlicenseNot gradedqualityDmaintenanceOpenSCAD wrapped as an MCP server. Render .scad with parameter overrides, run parametric sweeps, validate syntax, compute STL metrics. Curated by Archimedes Market with a verified Trust Report.3MIT
- AlicenseAqualityBmaintenanceEnables multimodal AI to convert photos with reference objects into parametric OpenSCAD models and watertight 3D-printable STL files, including calibration, part generation, and printability inspection.71MIT
TDQS
Scored across 2 tools
The two tools occupy clearly separate phases: list_models is pure discovery of schemas/presets/licenses, while generate performs rendering and returns artifacts. There is no plausible way to confuse them, and the descriptions reinforce the discovery-then-generate workflow.
list_models follows a clear verb_noun pattern, but generate is a bare verb with no object, so the convention is not uniform. It is still readable and predictable given only two tools.
Two tools is thin for a parametric CAD surface; discovery and rendering are covered, but anything beyond that (inspection, validation, artifact handling) has no entry point. The scope is defensible but feels minimal rather than well-scoped.
The core lifecycle (see what models exist, render one) is covered, but there is no get_model for drilling into a single schema, no explicit parameter/preset validation call, and no artifact listing or cleanup. Agents can work around this by reading list_models output, but the surface has notable gaps.