If you've searched for an MCP server for Blender, here's the short version: the de-facto standard is the community project ahujasid/blender-mcp (35k+ stars), now shipped under the package name mcp-for-blender. It opens a socket between a running Blender instance and an MCP client like Claude, and from there Claude drives your 3D scene directly — creating objects, setting materials, importing assets, running renders, and writing Blender Python for you. The entire install is four moves, and you can be issuing prompts in about five minutes. Here's the exact path, plus the one safety caveat worth stopping for.
The four-move install#
1. Install uv — the fast Python runner the server launches through. Use the official installer, not pip:
# macOS
brew install uv
# Windows
winget install --id=astral-sh.uv -e
# Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
You need Blender 3.0+ and Python 3.10+ as well. Don't go further until uv is installed — the README is blunt about that.
2. Add the server to your client. For Claude Code, it's one line:
claude mcp add blender uvx mcp-for-blender
For Claude Desktop, open Settings → Developer → Edit Config and add:
{
"mcpServers": {
"blender": {
"command": "uvx",
"args": ["mcp-for-blender"]
}
}
}
3. Install the Blender add-on — this is the piece that runs inside Blender and opens the socket:
uvx mcp-for-blender install-addon
Then in Blender: Edit → Preferences → Add-ons, and enable "Interface: MCP for Blender". (Prefer to do it by hand? Download addon.py from the repo and use Blender's Install… button.) There's also a uvx mcp-for-blender setup command that wires most of this in one shot.
4. Start the bridge. In Blender's 3D viewport, press N to open the side panel, select the "MCP for Blender" tab, and click "Start MCP Server." It listens on localhost:9876 by default. Restart your Claude client, and the blender tools show up.
A quick naming note so old tutorials don't trip you up: the project renamed fromblender-mcptomcp-for-blender, but the README confirmsuvx blender-mcpstill runs the server with no config change required. New installs should usemcp-for-blender; upgrade withuvx mcp-for-blender@latest update.
What Claude can actually do once it's wired#
This is where it stops being a party trick. The server gives Claude:
- Object and material control — create, transform, and shade geometry from a prompt.
- Visual verification — Claude can pull viewport, camera, multi-angle, wireframe, and render views, so it looks at its own work and corrects it instead of building blind. This is the single feature that makes agentic 3D usable.
- Asset import — search and pull ready-made assets from Poly Haven (HDRIs, textures, models), Sketchfab, and Poly Pizza.
- Text-to-3D generation — spin up new models through Tripo, Hunyuan3D, Hyper3D Rodin, or Meshy (some via a "Premium" path that needs no API key of your own).
execute_blender_code— write and run Blender Python directly. Everything above ultimately rides on this, which is exactly why it's the line to respect.
If you're new to wiring tools into Claude at all, this is a clean first MCP server to cut your teeth on — the pattern (a local server plus a one-line client command) is the same one behind running a local memory server over MCP, and the same decision tree in skill vs. subagent vs. MCP server tells you when an MCP server is the right tool reach in the first place.
The one caveat that matters#
execute_blender_code runs arbitrary Python inside Blender. The README says so directly — "powerful but potentially dangerous" — and tells you to save your work before using it. Two more facts decide how you deploy this safely:
- The socket server has no authentication or encryption. Keep it bound to
localhostand off untrusted networks. - Run one MCP client at a time against Blender — Claude Desktop or Cursor, not both.
Translated into practice: work in a throwaway .blend (or save first) before a big agent run, keep the bridge local, and treat the Blender process as what it is — a tool that can run code on your machine. That's the same posture any serious builder takes with an agent that touches a shell; the fact that the "shell" here renders a dragon doesn't change the rule. Within those lines, a Blender MCP server is one of the most genuinely fun — and useful — ways to put Claude's hands on something real.



