Blender 5 + Claude Code MCP

Part 2 — Install Blender MCP for Claude Code

Connect Blender 5 to Claude Code: install uv, add the blender-mcp server with claude mcp add, install addon.py via Install from Disk, and click Connect to Claude. No Python required.

In Part 1 you got comfortable with the Blender 5 interface. Now you will wire Blender up to Claude Code so that everything you do from here on is driven by natural-language prompts instead of clicks. This part installs the bridge and proves it works end to end.

There is exactly one thing to keep in your head: you are connecting two small programs — an add-on living inside Blender and a server that Claude Code launches — and then forgetting they exist. Once connected, you only ever talk to Claude.

Lesson 5: Understand the Architecture

Blender MCP has two halves. One half is a Blender add-on (a file called addon.py) that lives inside Blender and can touch the scene. The other half is an MCP server named blender-mcp that Claude Code launches via uvx. The two halves talk to each other over a local socket. Claude Code sends instructions down the chain; the add-on carries them out in your scene.

The full flow looks like this:

Claude Code  →  MCP server: blender-mcp  →  Blender MCP add-on  →  Blender scene

Read it left to right: you type a prompt into Claude Code, Claude calls the blender-mcp server, the server relays the request to the add-on running inside Blender, and the add-on makes the change in your scene. Information also flows back the other way — when Claude needs to know what objects exist, the add-on reports the scene back up the chain.

The MCP server happens to be written in Python, but you never write Python. Under the hood, uvx launches the server on Python 3.10+ — uv fetches and manages that runtime for you — so you never install or invoke Python yourself either. Every task in this tutorial is a natural-language prompt — nothing more.

Lesson 6: Install Requirements

You need four things in place: Blender 5 (the latest release — 5.0 shipped in November 2025), Claude Code, the uv package manager (which provides the uvx launcher), and the Blender MCP add-on. The add-on supports Blender 3.0 and newer, so it loads cleanly on Blender 5. You never write Python — uv fetches and runs the Python (3.10+) the server needs for you, so there is nothing to learn or set up there.

Install Blender 5 from blender.org and confirm Claude Code is already working in your terminal. Then install uv. On Windows, run this in PowerShell:

powershell -c "irm https://astral.sh/uv/install.ps1 | iex"

After it finishes, restart the terminal so the new uvx command is on your PATH. On macOS use brew install uv, and on Linux use curl -LsSf https://astral.sh/uv/install.sh | sh. Whichever platform you are on, verify the install with:

uvx --version

If that prints a version number, uvx is ready and Claude Code will be able to launch the blender-mcp server on demand.

On Windows, GUI-launched MCP clients sometimes fail to inherit your PATH and report spawn uvx ENOENT. If that happens later, point the config at the full path to uvx, or use a cmd wrapper: {"command":"cmd","args":["/c","uvx","blender-mcp"]}.

Lesson 7: Add Blender MCP to Claude Code

Register the server with Claude Code using one command:

claude mcp add blender uvx blender-mcp

This tells Claude Code: “there is an MCP server named blender; to start it, run uvx blender-mcp.” If you prefer to be explicit, the equivalent long form spells out the transport:

claude mcp add --transport stdio blender -- uvx blender-mcp

Here --transport stdio states that Claude Code talks to the server over standard input/output, and the -- separates Claude Code’s own options from the command it should run (uvx blender-mcp). Everything after -- is the server command, untouched by Claude Code’s argument parser.

Confirm the server is registered:

claude mcp list

You should see blender in the list. Then, inside a Claude Code session, run the built-in command to check its live status:

/mcp

This shows whether Claude Code can reach the blender server. It will not be fully connected to your scene yet — that final hop is the add-on, which you enable in the next lesson.

Lesson 8: Install the Blender Add-on (Blender 5 flow)

The add-on is the half that lives inside Blender. Note that the install menu changed in Blender 4.2, so this flow differs from older guides — there is no longer a bare “Install…” button to click. Follow these steps in order:

  1. Download addon.py from the Blender MCP repository (github.com/ahujasid/blender-mcp).
  2. In Blender, open Edit > Preferences > Add-ons.
  3. Click the dropdown chevron — the small v at the top-right of the Add-ons panel — then choose “Install from Disk…”.
  4. Select addon.py. Because it is a single .py file, it installs directly.
  5. Tick the checkbox next to “Interface: Blender MCP” to enable the add-on.
  6. Back in the 3D Viewport, press N to open the Sidebar.
  7. Open the BlenderMCP tab in the Sidebar.
  8. Click “Connect to Claude”.

Clicking “Connect to Claude” connects the add-on to the running MCP server over the localhost:9876 socket (the defaults are BLENDER_HOST=localhost and BLENDER_PORT=9876). From this point on you only type prompts to Claude Code — you never touch Python and never click through Blender’s menus by hand.

With the add-on connected and the server registered, the whole chain is live: Claude Code can now read your scene, create and modify objects, apply materials, organize collections, and export — all from the prompts you write next.

Exercise

Verify your full setup end to end. Run uvx --version and claude mcp list in your terminal, confirm blender appears, then start Claude Code and run /mcp to check the server status. Finally, in Blender, open the Sidebar with N, go to the BlenderMCP tab, and click “Connect to Claude”. When all four checks pass, your bridge is ready — without having written a single line of Python.