Claude Desktop + Blender via MCP: Real-Time 3D Workflow Closes the Feedback Loop

A developer wired Claude Desktop into Blender using the open-source blender-mcp add-on, which runs a Model Context Protocol server inside Blender. Once installed and registered in claude_desktop_config.json, Claude Desktop sees Blender as an MCP server with tools like get_scene_info, create_object, set_material, and render_image. No copy-paste needed.

Setup: Under 8 Minutes

1. Download the release ZIP from the GitHub repo.
2. In Blender: Edit > Preferences > Add-ons > Install → select ZIP → enable.
3. Press N in the viewport → BlenderMCP tab → Start Server.
4. In claude_desktop_config.json, add:

{
  "mcpServers": {
    "blender": {
      "command": "uvx",
      "args": ["blender-mcp"]
    }
  }
}

1. Restart Claude Desktop. The plug icon shows "blender" as connected.

Why It's Different

When the developer asked Claude to "render the current frame at 512 samples and tell me what's in the image," Claude called the render tool, read the output PNG via MCP's image tool, and described the lighting back. The model saw the result—closing the feedback loop that pure script-paste cannot.

Where It Excels

• Iterative composition: "more orange, less red, push the key light back 2 units"
• Scene inspection: "why is this object rendering black"
• Multi-step builds with mid-build correction: "the roof should be steeper" while Claude builds a cabin
• Visual confirmation: Claude actually looks at a render

Limitations

• Heavy production scenes: MCP runs in Blender's main thread, blocking the UI.
• Headless render farms: needs Blender open with the add-on running.
• Air-gapped machines: no Claude Desktop connection.
• For those cases, fall back to script-paste or blender -b file.blend -f 1.

Trust-but-Verify Rules

• Always work in Sandbox.blend first.
• Save before any complex multi-step prompt.
• The MCP add-on has a tool-allowlist—disable delete_object, clear_scene, and destructive modifier-apply when iterating. Re-enable only when needed. Claude may interpret "clean up" as deleting assets it doesn't recognize if prompts are ambiguous.

Key Surprise: Persistent Context

After 30 minutes of building a scene, asking "scale that material's noise frequency down by half" works—Claude remembers what "that material" refers to. With script-paste workflows, context is lost every prompt.

Tool Ecosystem

The developer used Claude Code (separate from Claude Desktop) to build non-real-time parts: render-farm orchestration scripts, custom panel add-ons, batch-renaming scripts for CAD imports.

Full Guide

The complete write-up covers five workflows (MCP, procedural geometry, batch ops, custom add-ons, render orchestration), failure modes with bpy, and a decision tree at clskillshub.com/blog/claude-blender-3d-modeling-workflow.