Blender MCP With Claude Code: Setup and Your First 3D Scene

Blender MCP is one of the most fun things you can wire into Claude Code: it turns "model a low-poly house with a red roof" into an actual 3D scene. It works by bridging two pieces — a Blender addon that opens a socket server inside Blender, and an MCP server that Claude Code talks to. Below is the complete setup for Blender MCP with Claude Code, what you can build once it's connected, and how to fix the connection issues people hit first.

What Blender MCP with Claude Code does

MCP — the Model Context Protocol — is how Claude Code connects to external tools. Blender MCP is one such tool: an open-source server that gives Claude two-way control of Blender. When you run Blender MCP with Claude Code, the agent can:

• Create, modify, and delete 3D objects by description
• Apply and edit materials and colors
• Set up scenes and lighting
• Inspect the current scene to understand what's there
• Run arbitrary Python in Blender for anything the built-in tools don't cover

The architecture is simple: a Blender addon runs a socket server inside Blender, and the MCP server is the bridge between that socket and Claude Code. Your prompts become Blender operations.

Prerequisites for Blender MCP with Claude Code

Before you start, make sure you have these three things installed. Getting them straight up front avoids most setup pain:

The one people miss is uv, a fast Python package manager. On Windows, install it with powershell -c "irm https://astral.sh/uv/install.ps1 | iex" and make sure uv is added to your PATH.

How to set up Blender MCP with Claude Code

With the prerequisites in place, setup is three moves:

1. Install the Blender addon. Download addon.py from the BlenderMCP repository. In Blender, open Edit → Preferences → Add-ons → Install, select addon.py, and enable the checkbox next to Interface: Blender MCP.
2. Register the MCP server with Claude Code. In your terminal, run:

   claude mcp add blender uvx blender-mcp

   This is the whole Claude Code side — the claude mcp add command tells Claude Code how to launch the Blender MCP server via uvx.
3. Start the server in Blender. Open the BlenderMCP panel in Blender's N-sidebar and click Connect / Start MCP server. Leave Blender open.

That's it — Blender MCP with Claude Code is now live. Start Claude Code, and it will list the blender tools as available. A quick test prompt like "create a cube and give it a blue metallic material" confirms the bridge is working end to end.

Using Blender MCP with Claude Code: what you can build

Once connected, you drive Blender in plain English. The sweet spot is describing what you want and letting Claude Code translate it into Blender operations:

Because Blender MCP can also run arbitrary Python inside Blender, there's almost no ceiling — anything Blender's Python API can do, Claude Code can request. That makes Blender MCP with Claude Code a genuine creative accelerator, not just a toy: rough out a scene by prompt, then refine by hand.

Troubleshooting Blender MCP with Claude Code

If Claude Code can't reach Blender, it's almost always one of these:

1. The Blender server isn't running. The addon's socket server must be started from the BlenderMCP panel, and Blender must stay open. This is the number-one cause of "connection failed."
2. The MCP server isn't registered. Confirm claude mcp add blender uvx blender-mcp ran successfully — list your servers to check Claude Code sees blender.
3. You ran uvx manually. Don't run the uvx blender-mcp command yourself in a separate terminal; let Claude Code launch it via the MCP config. Running it twice causes a port conflict.
4. uv isn't on your PATH. If uvx isn't found, re-check the uv install and PATH entry.

Work through those in order and the connection almost always comes back. For the broader picture of how Claude Code talks to tools, our Claude Code MCP guide covers the protocol in depth, and what is Claude Code explains the agent itself.

Real projects with Blender MCP and Claude Code

Once the connection is solid, the fun starts. Blender MCP with Claude Code shines for a few concrete workflows:

• Blocking out scenes fast. Describe a rough layout — "a small room with a desk, a chair, and a window" — and let Claude Code place the primitives. You get a greybox in seconds you'd otherwise build by hand, then refine it.
• Learning Blender by watching. Because the agent runs real Blender operations (and Python), you can ask it to do something and see exactly which tools and steps it used. It's a surprisingly good way to learn the app's API.
• Repetitive setup. Three-point lighting, a camera rig, a standard material library — the boilerplate of every scene — becomes a one-line request instead of a manual checklist.
• Procedural experiments. Ask for "twenty cubes in a spiral with random colors" and Claude Code writes the Python to generate it. Iterating on procedural ideas by prompt is far faster than scripting from scratch.

The honest limits are worth knowing too. Blender MCP with Claude Code is excellent at structure — objects, materials, transforms, scene setup — but it's not a substitute for an artist's eye on final polish. Think of it as a very capable technical assistant: it handles the mechanical 90% so you spend your time on the creative 10%.

A practical tip: keep Blender visible on a second monitor while you work. Watching the scene update as Claude Code executes each step makes it obvious when a prompt was misread, so you can correct course immediately rather than discovering it three operations later. And because everything runs through MCP, you can combine the Blender server with your other tools in the same session — that composability is what makes Blender MCP with Claude Code more than a novelty.