mcp-for-blender-pro
An AI assistant and MCP server for Blender with visual chat, scene inspection and editing tools, multi-agent workflows, and support for OpenAI, Claude, Gemini, Ollama, OpenCode, and custom endpoints.
Visit LiCinCan/blender-ai-mcp-addonOverview
mcp-for-blender-pro is an AI assistant and MCP server for Blender. It combines a visual chat workspace, scene tools, model choice, and agent workflows so users can inspect scenes, build objects, edit materials, find assets, and carry out multi-step operations while continuing to work in Blender.
Key Features
- Scene and object inspection gives the assistant context before it acts.
- A visual Studio workspace provides chat, scene objects, viewport snapshots, approvals, and a task board.
- Users can connect supported cloud providers, local Ollama models, or compatible custom endpoints.
- A single assistant can handle quick changes, while a team chain supports managers, workers, and reviewers for structured tasks.
- A built-in MCP server connects OpenCode and other clients supporting authenticated Streamable HTTP MCP.
- 21 scene tools support creating, inspecting, editing, capturing, searching assets, consulting Blender APIs, and exporting scenes.
Use Cases
- Artists who want faster iteration in Blender.
- Technical artists who automate repetitive work.
- Developers connecting AI tools to Blender.
Getting Started
- Download mcp-for-blender-pro.zip from Releases.
- In Blender, open Edit, then Preferences, then Get Extensions, then the menu, then Install from Disk.
- Select the ZIP, enable mcp-for-blender-pro, then open 3D Viewport and the N panel for MCP Pro.
- Choose a provider, add connection details, and select a model.
- Send a message in Blender or click Open Studio Window.
Deployment & Requirements
- The release bundle targets Windows x64 with Blender 4.2 or later.
- Keep Blender open while using Studio or an external client.
Before You Adopt
- License: MIT. Review its terms before using, modifying, or distributing the project.
- Python tool validation is a guardrail, not a security sandbox.
- Approval behavior for external MCP clients is managed by those clients.
- Asset integrations may require service keys, and users must follow asset licenses.
- Studio and external client use requires Blender to remain open.
