Blender MCP Integration
Read the shared execution guidance once per task for autonomous decisions, evidence cadence, and long-task continuity.
Use the narrowest MCP layer that improves the task.
Choose the layer
- Prefer Blender's official Lab MCP for Blender 5.1+ live scene inspection, screenshots, documentation lookup, rendering, navigation, and Python execution.
- Use Blender Agent Studio's MCP for deterministic batch inspection, standardized geometry evidence, and bounded authored-scene renders.
blender_render_scenepreserves cameras, lights, volumes and color management and returns the first image inline;inspectOnlydiscovers scene settings before rendering. The bundled Poly Haven search/download tools also acquire verified CC0 textures and HDRIs without another add-on or API key; see the rendering workflow for material setup and standalone CLI use. - Consider
ahujasid/blender-mcponly when the request needs its additional remote-host, Poly Haven, Sketchfab, or external 3D-generation integrations and accepts the extra installation, network, credential, and telemetry surface. - Do not run multiple add-on socket servers on the same host/port.
Read references/mcp-options.md before installing or replacing a Blender add-on.
Preserve reproducibility
- Keep the durable model in a Python source file even when using live MCP execution.
- Save a new
.blendbefore risky arbitrary-code operations. - Use official MCP screenshots for interactive iteration.
- Use
$blender-agent-studio:blender-asset-validationfor final clean-process inspection and fixed evidence cameras. - Record which MCP tools were used in benchmark runs.
Benchmark MCP value
Compare:
- plugin skills with MCP tools unavailable;
- the same skills with the candidate MCP enabled.
Keep task, model, effort, time budget, and evaluator identical. Count execution failures, recovery turns, time, and final asset quality. Retain an MCP dependency only when it improves outcomes or materially reduces reliable completion cost.
