← Index

three.ws Blender

io.github.nirholas/blender-mcpv0.5.0Cloud Storage

Drive a local Blender headlessly: inspect, convert, render and script 3D files.

The current version, v0.5.0, was published to the official MCP registry on 2026-09-30. It is distributed as @three-ws/blender-mcp on npm, filed under Cloud Storage by this index, and declares 10 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using three.ws Blender in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-30).

Contracts can change after screening, with no version bump. The gate pins three.ws Blender’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
BLENDER_PATH

Absolute path to the Blender 3.0+ executable. Leave unset to discover it on PATH and at the platform's standard install locations.

BLENDER_MCP_TIMEOUT_MS

Ceiling for one Blender job in milliseconds. Renders and heavy conversions are the slow ones.

BLENDER_MCP_WORKDIR

Directory for outputs written when a tool is called without an explicit output path.

BLENDER_MCP_ALLOW_PYTHON

Set to 0 to withdraw blender_run_python, which executes caller-supplied Python inside Blender, from the advertised tool list.

BLENDER_MCP_INLINE_IMAGE_BYTES

Ceiling on inlined image bytes. Past this the image stays on disk and the response says where.

BLENDER_MCP_INLINE_IMAGE_PX

Longest edge of the render copy returned inline in a tool result. The full-resolution PNG is always written to disk.

BLENDER_MCP_MAX_CONCURRENCY

How many Blender processes may run at once. Further calls queue rather than compete for memory.

THREE_WS_BASE

Base URL of the three.ws deployment backing blender_forge_import.

THREE_WS_FORGE_TIMEOUT_MS

Ceiling for one text-to-3D generation in milliseconds.

THREE_WS_FORGE_PROVIDER_KEY
secret

Meshy/Tripo API key for the bring-your-own-key geometry lane. The default image lane is free and needs no key.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
25
installability
25
documentation
15
stability
5
Alternatives in Cloud Storage