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

To use Blender MCP with Claude Code, install the BlenderMCP addon in Blender, then run claude mcp add blender uvx blender-mcp to register the MCP server. Once Blender's server is running and Claude Code is connected, you can create objects, apply materials, set up lighting, and run Python in Blender — all from natural-language prompts. You'll need Python 3.10+, Blender 3.0+, and the uv package manager.

Setup commands verified 31 July 2026 against Anthropic's Claude Code MCP documentation.

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. When we have set this up ourselves, the connection step is where it trips up almost every time, and it is nearly always one of two things: the Blender addon's socket server was never actually started inside Blender, or uv is not on the path Claude Code can see. Check those two before you touch anything else — they account for the overwhelming majority of "it won't connect" reports. The other lesson from doing this ourselves is to start far smaller than you want to. The temptation is to prompt a whole scene on the first try, but the runs that actually succeed begin with one object — "add a cube, give it a red material" — so you can confirm the round trip works before you ask for anything ambitious. Once a single command lands cleanly in Blender, you know the bridge is solid and can scale up the requests with confidence; when a big prompt fails, you have no idea which of the ten steps broke. Build the habit of one verifiable change at a time and the whole workflow stops feeling fragile. If the server itself refuses to register in the first place, our walkthrough on adding an MCP server to Claude Code covers the claude mcp add flags and scopes in more detail. Before writing this up we did it ourselves, which is why the small snags are called out where they actually occur.

What Blender MCP with Claude Code does

The bridge gives Claude two-way control of Blender: it can create, modify, and delete 3D objects, apply and edit materials, set up scenes and lighting, inspect what is already there, and run arbitrary Python through Blender's API.

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: Blender, Python, and uv

You need three things before setup: Blender 3.0 or newer, Python 3.10 or newer, and the uv package manager that launches the server. uv is the one people miss — confirm it is on your PATH.

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

Three moves: install addon.py from the BlenderMCP repository and enable "Interface: Blender MCP", run claude mcp add blender uvx blender-mcp in your terminal, then start the socket server from Blender's N-sidebar panel and leave Blender open.

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.

What you can build once it's connected

You drive Blender in plain English — low-poly meshes, three-point lighting, material edits, scene descriptions. Because the server can also run arbitrary Python, anything Blender's API exposes is reachable from a prompt.

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 the connection

Four causes account for nearly every failure: the addon's socket server was never started, the MCP server was never registered, you launched uvx blender-mcp yourself and caused a port conflict, or uv is missing from your PATH.

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

The strongest workflows are blocking out rough scenes, learning Blender by watching real operations run, automating repetitive lighting and camera setup, and prototyping procedural experiments. It handles structure well; final artistic polish still needs you.

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.

Building games rather than scenes? The same MCP idea drives Claude in Roblox Studio, where Studio now ships its own server.