SkillAgentSearch skills...

mcp-openscad-render-loop

OpenSCAD wrapped as an MCP server. Render .scad source with parameter overrides, run parametric sweeps, validate syntax, extract module signatures, and compute STL metrics (bounding box, volume, surface area). Designed so an agent can iterate on para

Install / Use

claude mcp add archimedes-market -- npx -y github:archimedes-market/mcp-openscad-render-loop

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

72/100

Supported Platforms

Claude Code
Claude Desktop

Our assessment of mcp-openscad-render-loop

mcp-openscad-render-loop scores 72/100 on our quality scale, 3779th of 4,607 Development & Engineering skills we index.

Its MCP Server is 3.3 KB long, well organised into 10 sections with 3 code examples: a solid amount of guidance for an agent.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
3/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 5 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 90/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

mcp-openscad-render-loop compared with similar skills

All 4 of these similar skills score higher than mcp-openscad-render-loop; compare them before choosing.

SkillScoreStarsUpdatedFormat
mcp-openscad-render-loop (this skill)by archimedes-market7235mo agoMCP Server
Agent-Reachby Panniantong10098.8k2d agoCLAUDE.md
taste-skillby Leonxlnx10098.5k3d agoCLAUDE.md
headroomby headroomlabs-ai10075.6ktodayCLAUDE.md
ai-job-searchby MadsLorentzen10050.7ktodayCLAUDE.md

Frequently asked questions

How do I install mcp-openscad-render-loop?
Run claude mcp add archimedes-market -- npx -y github:archimedes-market/mcp-openscad-render-loop. The install tabs above show the steps for each supported agent.
Which AI agents does mcp-openscad-render-loop work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is mcp-openscad-render-loop safe to use?
It is MIT-licensed and scores 90/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is mcp-openscad-render-loop still maintained?
The repository was last updated about 5 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

Archimedes Trust Report — VERIFIED 92/100

Verified asset on Archimedes Market. View the full 4-dimension Trust Report (security · quality · license · complexity) and the curated catalog on the asset page.


MCP OpenSCAD Render Loop

OpenSCAD wrapped as an MCP server so an agent can iterate on parametric CAD designs without bouncing in and out of the GUI. Render .scad source with parameter overrides, run parameter sweeps, validate syntax, extract module signatures, and compute STL geometry metrics.

Tools

  • render_stl — render a .scad file or inline source to STL with -D parameter overrides
  • render_png — preview render to PNG with camera + image-size control
  • parametric_sweep — Cartesian sweep over one or more parameter ranges, returns a manifest of outputs
  • validate_scad — syntax check via openscad --check (no render)
  • list_modules — extract top-level module foo(...) and function bar(...) signatures with defaults
  • compute_metrics — bounding box, volume, surface area, triangle count from an STL

Why this server exists

OpenSCAD's CLI is well-designed but verbose. Most agent CAD workflows do the same loop: edit parameters → render → measure → adjust. This server collapses that to one tool call per iteration and returns geometry metrics directly so the agent doesn't have to parse STL bytes itself.

Quick start

# 1. Install OpenSCAD (must be on PATH)
brew install openscad      # macOS
apt-get install openscad   # Debian/Ubuntu

# 2. Install the MCP server
pip install mcp-openscad-render-loop

# 3. Set output directory and run
export MCP_OPENSCAD_OUTPUT_DIR="/tmp/scad-renders"
mcp-openscad-render-loop serve

Claude Desktop config:

{
  "mcpServers": {
    "openscad": {
      "command": "mcp-openscad-render-loop",
      "args": ["serve"],
      "env": {
        "MCP_OPENSCAD_OUTPUT_DIR": "/tmp/scad-renders",
        "MCP_OPENSCAD_BINARY": "/usr/local/bin/openscad"
      }
    }
  }
}

Typical agent workflow

Agent: "Design an enclosure for a 60x40x15mm PCB with 2mm walls and M3 mounting posts."
↓
1. list_modules on enclosure.scad → finds module enclosure(pcb_l, pcb_w, pcb_h, wall, post_dia)
2. render_stl with pcb_l=60, pcb_w=40, pcb_h=15, wall=2, post_dia=3 → enclosure_v1.stl
3. compute_metrics on enclosure_v1.stl → bbox 66x46x21, volume 18.4cm³, 1,240 triangles
4. parametric_sweep on wall ∈ [1.5, 2.0, 2.5] → 3 STLs + metrics → wall=2 is the strength/weight knee
5. render_png at iso camera → preview image attached to agent's reply

Safety

  • MCP_OPENSCAD_OUTPUT_DIR is the only writable path. Any output path outside this dir is rejected.
  • Each render is hard-capped at 60 seconds (configurable). Long sweeps run renders sequentially, not in parallel — keeps memory bounded.
  • Inline .scad source is written to a temp file inside the output dir; nothing executes outside openscad.
  • No import("/some/path.dxf") traversal — relative paths in .scad are resolved against the output dir or the source file's dir, never against /.

License

MIT.

Related Skills

View on GitHub
GitHub Stars3
CategoryDevelopment
Updated5mo ago
Forks0

Languages

Python

Trust signals

90/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low1 info