| name | use-blender-mcp |
| description | Drive blender-mcp for design-anything work — Drive Blender from any LLM via MCP — the natural execution backbone from agent to printable geometry. Use when a design task routes to this tool (agent-infrastructure). GENERATED satellite skill: facts fetched 2026-07-19; treat as a pointer, not gospel.
|
| kind | skill |
| license | MIT |
| runtimes | ["claude-code","codex","hermes"] |
| generated | true |
use-blender-mcp — satellite of ahujasid/blender-mcp
GENERATED by scripts/satellites.py build from data/satellites.yml —
edit the data or KNOWLEDGE.md, never this file (drift-gated).
Verified facts (as of 2026-07-19)
How to use it
- Read
KNOWLEDGE.md in this folder — the SHA-pinned deep digest (architecture, how to drive it, gotchas, verify command).
- Supply-chain rules (non-negotiable): this is external code — read before
running, prefer ephemeral use over persistent install, human-gate anything
that executes. Popularity (24,462 stars) is not a safety proof.
- Route outputs back through the matching design-anything gate — a satellite
generates; only our gates say "ready".
Verification (eval-with-teeth)
Facts above are verifiable against the live API:
gh api repos/ahujasid/blender-mcp --jq .stargazers_count. The digest's claims are
pinned to 6641189231ca; if status is STALE, re-verify before
relying on internals. Success of any run is judged by OUR gate's exit 0.
Honest edges
A satellite is a pointer + pinned digest, never a vendored copy: upstream can
change, relicense, or die — the weekly freshness sync measures that instead of
promising otherwise.
