Blender add-on turns an AI assistant into a scene editor
An MIT-licensed Blender add-on, mcp-for-blender-pro, lets an AI assistant inspect a scene, create objects, assign materials, capture viewport screenshots and run multi-step tasks, with 21 built-in tools and an MCP server for external clients.
Image: GitHub
Why it mattersA 3D artist can now describe a scene and have an assistant build it inside Blender rather than scripting the operations by hand, which widens the audience that can automate repetitive scene work.
A Blender add-on called mcp-for-blender-pro reached 713 GitHub stars in three days by giving the 3D application a conversational AI assistant. The repository, published as LiCinCan/blender-ai-mcp-addon under an MIT licence, pairs a chat panel inside Blender with 21 built-in scene tools and a Model Context Protocol server for outside clients.
The README positions it for artists who want faster iteration, technical artists who automate repetitive work and developers who want to connect AI tools to Blender. The project ships as a developer release 1.0.0 for Windows x64 running Blender 4.2 or later.
What the assistant can do
The tool list in the README covers scene inspection, object creation, material editing, viewport capture, asset search, consulting Blender's Python API and exporting the scene. The assistant reads the current scene before it acts, so the model has context about what already exists in the file. A visual workspace called Studio runs beside Blender with the chat, scene objects, viewport snapshots, an approval view and a task board.
The maintainers describe two work modes. Single assistant handles direct, conversational edits. A Team chain splits a request between three roles: a manager that breaks a task into assignments and acceptance criteria, workers that run the scene operations, and reviewers that inspect the result and either approve the work or return specific findings. Tasks run sequentially, a blocked task gets one correction attempt, and a second failed review stops the workflow.
Which models are supported
The README lists OpenAI, Anthropic Claude, Google Gemini, OpenRouter, OpenCode Zen, Ollama and custom APIs as supported connections. Custom endpoints speak the OpenAI Chat Completions, Anthropic Messages and Ollama protocols. The maintainers note that models with tool-calling support are required for scene operations, and that image-capable models can read viewport screenshots.
The project also ships OpenCode Portable, which the maintainers describe as a sidebar launcher for the OpenCode client with the Blender connection pre-configured. Other MCP-compatible clients can connect to the authenticated local endpoint the add-on exposes.
The claims the maintainers make, and the ones they do not
The maintainers mark the project as a release 1.0.0 and recommend keeping Blender open while using Studio or an external client. They do not quote any benchmark, time-to-task measurement, or vendor comparison, and the README's example prompts are modest: inspecting a scene, creating a product-display layout, duplicating an object into a row and asking before importing a Poly Haven asset.
For a Blender user already paying for a model subscription, the trade is a Blender add-on installation and a connection setup against a familiar language-model bill. The result is a scripted scene described in prose instead of in Python, with the viewport as the check on whether the model understood the request. That is a small enough change that the practical test is one scene a user already builds by hand this week.
Source
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.