MCP for Blender

MCP for Blender turns Blender into something an LLM can drive. It is a community project, not a Blender Foundation product, and the repository carries that disclaimer directly under the title. The idea is simple: a socket server inside Blender plus an MCP server outside it, so Claude Code, Codex, Cursor, or any other MCP client can create objects, change materials, inspect the scene, and run Python inside a live Blender session.

The first-party repository was created on 2025-03-07 under MIT. On 2026-09-20 GitHub listed 29,059 stars and 2,669 forks, with the last push on 2026-09-16. The project was renamed from blender-mcp to mcp-for-blender; the PyPI package is now mcp-for-blender, while uvx blender-mcp still runs the server and needs no config change. The product site is mcp-for-blender.com. Stars measure attention, not installs.

The disclosure matters here more than for most tools. The Blender addon can execute arbitrary Python sent by the model, so the project asks you to run a single server instance and to treat the connection as local-only.

Key Features

• Two-way socket link: the addon listens inside Blender and the MCP server talks to it, so the agent works on the scene you have open, not a headless copy.
• Object and material control: create, modify, and delete objects, and apply or change materials and colors from a prompt.
• Scene inspection: the agent can ask what is actually in the file before it changes anything, which is what stops most blind edits.
• Python execution: arbitrary Blender Python in the running session, which is the escape hatch for anything the preset tools do not cover.
• Asset and model generation: Poly Haven assets, Sketchfab models, Poly Pizza low-poly models, plus AI-generated meshes through Hyper3D Rodin and Hunyuan3D.

Use Cases

• Blockout in natural language: describe a scene, get primitives placed and lit, then refine by hand.
• Repetitive scene surgery: rename, hide, parent, or re-materialise dozens of objects without clicking through the outliner.
• Asset round trips: pull a Poly Haven HDRI or a Sketchfab model in and have the agent wire it into the shader graph.
• Pipeline scripting: let the model write and run the Blender Python you would otherwise look up.

Limitation: the tool is only as good as the model driving it, and 3D work needs spatial judgement that text models still fumble. Give it tight prompts, keep a save before big operations, and remember that an MCP client with Python access to Blender is a large trust surface.

Pricing

The project is supported by sponsors including CodeRabbit, Vercel's Guillermo Rauch, and Kevin Guanche Darias. Sponsorship and a "buy me a coffee" link are the only funding paths listed.

Getting Started

# 1. install uv
brew install uv                      # macOS; use the official installer elsewhere

# 2. register the server with your MCP client
claude mcp add blender uvx mcp-for-blender
# or: codex mcp add blender -- uvx mcp-for-blender

# 3. install and enable the Blender addon
uvx mcp-for-blender install-addon

In Blender, enable Interface: MCP for Blender under Add-ons, then press N in the 3D viewport, open the MCP for Blender tab, and click Start MCP Server. First-party docs: the repository README and mcp-for-blender.com.

Frequently Asked Questions

Do I need to rename anything after the blender-mcp change?

No. Existing configurations keep working and uvx blender-mcp still starts the server. New installs should use the mcp-for-blender package name.

Can I run Claude Desktop and Cursor against it at the same time?

The project says no. Run one server instance at a time.

Is it official Blender software?

No. The README states plainly that it is a third-party integration and not made by Blender.

Alternatives

• Hyper3D Rodin: text or image to 3D meshes when you need generation rather than scene control.
• MCP Framework: the toolbox for writing your own MCP server instead of adopting this one.
• Blender itself: the free application this project plugs into.

Tips

1. Ask the agent to inspect the scene before it edits. The scene-inspection tools exist precisely so it does not guess object names.
2. Save first. A model with Python access to Blender can do real damage to a scene in one call.
3. Combine it with a generator: let Rodin or Hunyuan3D produce the mesh, then use the agent for placement, materials, and render settings.

Conclusion

MCP for Blender is the practical bridge between text models and actual 3D software: a socket, an addon, and a small set of tools that let an agent work on the scene you have open. Try it for blockouts, scene cleanup, and asset wrangling. Keep it local, keep one instance, and save before you let it loose on a finished scene.