Blender MCP setup
Use the Blender MCP tools exposed by the user's configured Blender setup to inspect and control Blender. Do not assume a particular MCP implementation, endpoint, port, operating system, or OVRTX runtime package.
When to Use
Use when a user is new to Blender MCP, asks to create or edit a scene through MCP, or reports that Blender tools cannot connect. This covers the Blender-side MCP connection only; OVRTX and OVPhysX runtime setup belongs to ovrtx-addon-install-and-preflight.
Prerequisites
- Blender 5.2 or newer is required for the OVRTX example.
- Blender is running with the user's Blender MCP add-on/server enabled.
- The agent has access to scene inspection, Blender-Python execution, and (when available) a viewport screenshot tool.
The MCP server and the OVRTX worker are separate services. A working MCP connection does not prove OVRTX is installed, and an OVRTX preflight failure is not fixed by changing MCP settings.
Blender Python and MCP mutation tools have local-code authority. Use a
user-scoped, access-controlled endpoint, expose it only as required by the
user's deployment, and do not connect to an endpoint whose owner is unknown.
Instructions
- Discover the Blender MCP tools available in this session. Prefer the provider's scene-info/status call before executing code.
For an untrusted
.blend, first follow
blender-content-safety-and-privacy: use an isolated Blender profile and
open with automatic script execution disabled.
- Make one non-destructive probe: read the Blender version, current file path (if any), active render engine, active camera, and object count. Do not clear or alter the scene during setup.
- If the provider exposes a screenshot call, capture the current viewport and report whether it is a 3D View, camera view, or another editor.
- Confirm the control loop with a harmless read-only Blender expression (for example,
bpy.app.version_string). Only after the user asks for scene work should you execute mutations.
- Summarize the facts needed for the next requested action: connection status,
Blender version, current file or “unsaved,” engine, active camera, and any
missing capability. Do not create a separate report artifact unless asked.
Concrete adapter calls
Discover equivalent tools when a provider uses other names. With the common
Blender MCP adapter, use this exact sequence:
mcp__blender__get_scene_info({})
mcp__blender__execute_blender_code({"code": "import bpy, json\nprint(json.dumps({'blender': bpy.app.version_string, 'file': bpy.data.filepath or None, 'engine': bpy.context.scene.render.engine, 'camera': bpy.context.scene.camera.name if bpy.context.scene.camera else None, 'objects': len(bpy.data.objects)}))"})
mcp__blender__get_object_info({"object_name": "GEO-target"})
mcp__blender__get_viewport_screenshot({"max_size": 800})
The object-info call is conditional on a known target. Load
blender-python-execution for the complete provider contract, paste-ready
probes, mutation transactions, and recovery rules.
Working rules
- Execute Blender Python in small, independently verifiable chunks. Re-import modules in each call; do not rely on variables surviving between calls.
- Never call
time.sleep() inside executed Blender Python. It blocks Blender's
main thread and prevents redraw or renderer progress. Split write, external
wait/poll, and read into separate tool calls.
- Address objects and datablocks by stable names, not selection order. Preserve existing user content unless deletion is explicitly requested.
- After every meaningful mutation, inspect the resulting object/camera/render state and take a viewport or render screenshot when available.
- Save a user-requested copy before destructive operations. Keep generated renders in a user-selected output directory.
- If Blender MCP is unavailable, stop at diagnosis and tell the user to start Blender, enable the MCP add-on, and verify the endpoint configured by their MCP deployment. Do not install an unrelated server or guess a port.
- Use the documented setup and runtime diagnostics. Runtime binaries and native clients are prerequisites handled by the OVRTX add-on.
- Do not enable embedded scripts, handlers, scripted drivers, or unknown
add-ons merely to make an untrusted scene load or evaluate.
Common failures
- Cannot connect: Blender is closed, the MCP add-on is disabled, the endpoint is wrong, or another process owns the endpoint. Ask the user to check those items in their deployment.
- Scene info works but code fails: report the exact Blender traceback and retry with a smaller chunk; do not repeatedly resend a large script.
- Screenshot is unavailable: continue with structured scene inspection, but mark visual validation as unavailable.
- MCP works but OVRTX does not render: switch to
ovrtx-addon-install-and-preflight; this is not an MCP connection problem.
1---2name: blender-mcp-setup3description: Connect an agent to a running Blender session through the user's Blender MCP server and verify a safe, usable scene-control loop. Use when a user is new to Blender MCP, asks to create or edit a scene through MCP, or reports that Blender tools cannot connect. This covers the Blender-side MCP connection only; OVRTX and OVPhysX runtime setup belongs to ovrtx-addon-install-and-preflight.4license: "Apache-2.0"5metadata:6 source: https://skillmd.com/skills/nvidia-omniverse/blender-mcp-setup7 author: "Max Bickley"8 version: "0.1"9 team: "omniverse"10 domain: "physical-ai"11 tags:12 - blender13 - omniverse14 - ovrtx15 - mcp16---1718# Blender MCP setup1920Use the Blender MCP tools exposed by the user's configured Blender setup to inspect and control Blender. Do not assume a particular MCP implementation, endpoint, port, operating system, or OVRTX runtime package.2122## When to Use2324Use when a user is new to Blender MCP, asks to create or edit a scene through MCP, or reports that Blender tools cannot connect. This covers the Blender-side MCP connection only; OVRTX and OVPhysX runtime setup belongs to ovrtx-addon-install-and-preflight.2526## Prerequisites2728- Blender 5.2 or newer is required for the OVRTX example.29- Blender is running with the user's Blender MCP add-on/server enabled.30- The agent has access to scene inspection, Blender-Python execution, and (when available) a viewport screenshot tool.3132The MCP server and the OVRTX worker are separate services. A working MCP connection does not prove OVRTX is installed, and an OVRTX preflight failure is not fixed by changing MCP settings.3334Blender Python and MCP mutation tools have local-code authority. Use a35user-scoped, access-controlled endpoint, expose it only as required by the36user's deployment, and do not connect to an endpoint whose owner is unknown.3738## Instructions39401. Discover the Blender MCP tools available in this session. Prefer the provider's scene-info/status call before executing code.41 For an untrusted `.blend`, first follow42 `blender-content-safety-and-privacy`: use an isolated Blender profile and43 open with automatic script execution disabled.442. Make one non-destructive probe: read the Blender version, current file path (if any), active render engine, active camera, and object count. Do not clear or alter the scene during setup.453. If the provider exposes a screenshot call, capture the current viewport and report whether it is a 3D View, camera view, or another editor.464. Confirm the control loop with a harmless read-only Blender expression (for example, `bpy.app.version_string`). Only after the user asks for scene work should you execute mutations.475. Summarize the facts needed for the next requested action: connection status,48 Blender version, current file or “unsaved,” engine, active camera, and any49 missing capability. Do not create a separate report artifact unless asked.5051## Concrete adapter calls5253Discover equivalent tools when a provider uses other names. With the common54Blender MCP adapter, use this exact sequence:5556```text57mcp__blender__get_scene_info({})58mcp__blender__execute_blender_code({"code": "import bpy, json\nprint(json.dumps({'blender': bpy.app.version_string, 'file': bpy.data.filepath or None, 'engine': bpy.context.scene.render.engine, 'camera': bpy.context.scene.camera.name if bpy.context.scene.camera else None, 'objects': len(bpy.data.objects)}))"})59mcp__blender__get_object_info({"object_name": "GEO-target"})60mcp__blender__get_viewport_screenshot({"max_size": 800})61```6263The object-info call is conditional on a known target. Load64`blender-python-execution` for the complete provider contract, paste-ready65probes, mutation transactions, and recovery rules.6667## Working rules6869- Execute Blender Python in small, independently verifiable chunks. Re-import modules in each call; do not rely on variables surviving between calls.70- Never call `time.sleep()` inside executed Blender Python. It blocks Blender's71 main thread and prevents redraw or renderer progress. Split write, external72 wait/poll, and read into separate tool calls.73- Address objects and datablocks by stable names, not selection order. Preserve existing user content unless deletion is explicitly requested.74- After every meaningful mutation, inspect the resulting object/camera/render state and take a viewport or render screenshot when available.75- Save a user-requested copy before destructive operations. Keep generated renders in a user-selected output directory.76- If Blender MCP is unavailable, stop at diagnosis and tell the user to start Blender, enable the MCP add-on, and verify the endpoint configured by their MCP deployment. Do not install an unrelated server or guess a port.77- Use the documented setup and runtime diagnostics. Runtime binaries and native clients are prerequisites handled by the OVRTX add-on.78- Do not enable embedded scripts, handlers, scripted drivers, or unknown79 add-ons merely to make an untrusted scene load or evaluate.8081## Common failures8283- **Cannot connect:** Blender is closed, the MCP add-on is disabled, the endpoint is wrong, or another process owns the endpoint. Ask the user to check those items in their deployment.84- **Scene info works but code fails:** report the exact Blender traceback and retry with a smaller chunk; do not repeatedly resend a large script.85- **Screenshot is unavailable:** continue with structured scene inspection, but mark visual validation as unavailable.86- **MCP works but OVRTX does not render:** switch to `ovrtx-addon-install-and-preflight`; this is not an MCP connection problem.