cadloop-openscad
Related Servers
Alternatives to cadloop-openscad
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to create and manipulate 3D models using OpenSCAD through MCP tools for code-based modeling, preview, and export.1MIT
- 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 gradedqualityBmaintenanceEnables AI agents and software to create, edit, inspect, validate, and export CAD geometry through MCP using backend-neutral typed operations, with FreeCAD/OpenCascade as the authoritative B-rep backend and JSCAD preview.1Apache 2.0
- 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
- AlicenseAqualityDmaintenanceEnables AI assistants to create and manipulate 3D CAD models using OpenSCAD.415 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEnables agents to validate, render preview (PNG), and export OpenSCAD models to various formats using the openscad CLI.76 npmMIT
TDQS
Scored across 9 tools
Most tools are clearly distinct: file ops (list/read/write), diagnostics (check, echo), and output tools (render, measure, preview). The main overlap is render vs measure vs preview, since render to STL also reports bounding box and volume and render to PNG overlaps with preview, but the descriptions explicitly delineate when to use each.
File operations follow a clean verb_noun pattern (list_files, read_file, write_file), but the evaluation tools are bare verbs (check, echo, render, measure, preview) and openscad_info is a noun-style name. Two internally consistent clusters, but the set mixes conventions overall.
Nine tools is well-scoped for an OpenSCAD workspace server, with each tool covering a distinct workflow stage (environment info, file I/O, syntax check, value extraction, and several render/measure variants). No tool feels redundant or padded.
The surface covers the full edit-check-render-inspect lifecycle for CAD scripts. Minor gaps exist, such as no delete/rename/move file operation and no explicit export-to-multiple-formats batch, but agents can work around these via write_file and render.