Blender MCP Server – AI 3D Modeling and Scenes
BlenderMCP is a community-maintained integration that connects MCP-compatible AI assistants to Blender through a local server and Blender add-on. Use it for prompt-assisted 3D modeling, scene creation, object manipulation, material changes, asset placement, and Blender automation.
Overview
BlenderMCP connects MCP-compatible AI assistants to Blender through a local MCP server and a Blender add-on. The MCP server receives tool calls over stdio, while the add-on runs inside Blender and exposes a socket-based connection for scene inspection and command execution. This lets an AI assistant work with the active Blender scene instead of only describing modeling steps.
What the MCP server enables
The documented integration supports prompt-assisted 3D creation and manipulation. Depending on the enabled add-on features and connected services, an AI agent can:
- Inspect the current Blender scene and retrieve object information.
- Create, modify, reposition, and delete 3D objects.
- Create and update materials, colors, lighting, and camera placement.
- Execute Python code inside Blender for advanced or unsupported operations.
- Retrieve models, textures, and HDRIs from Poly Haven when that integration is enabled.
- Search and download supported Sketchfab assets.
- Generate 3D models through Hyper3D Rodin or Hunyuan3D integrations where configured.
- Use Blender viewport screenshots as visual context for scene understanding.
- Assist with composition, studio lighting, isometric views, asset placement, and scene prototyping.
When to use it
Use BlenderMCP when a designer, artist, or developer wants to build or revise 3D scenes through natural-language instructions. Practical workflows include low-poly scene generation, environment blocking, material changes, lighting setup, camera composition, importing external assets, generating draft models, and preparing Blender scenes for visualization or downstream web and game workflows.
Connection and authentication
The documented MCP connection uses local stdio with:
uvx blender-mcp
Blender 3.0 or newer, Python 3.10 or newer, and the uv package manager are required. The bundled Blender add-on must be installed and enabled, then started from the BlenderMCP tab in the 3D View sidebar.
The MCP server communicates with the add-on over a local TCP socket. BLENDER_HOST and BLENDER_PORT can override the default connection values of localhost and 9876. No API key is required for core local Blender access, although optional services such as Hyper3D may require their own credentials or account limits.
Key considerations
This is a third-party integration and is not made by Blender. The execute_blender_code tool can run arbitrary Python inside Blender, so it should be treated as highly privileged. Save work before using write operations, review generated code, and avoid untrusted prompts or files. Only one MCP server instance should connect at a time. Complex operations may need to be broken into smaller steps. The project also documents anonymous telemetry; users can disable it completely by setting DISABLE_TELEMETRY to true.
Supported Transports
stdio
Command: uvx
Args:
blender-mcp
Frequently Asked Questions
- When should an AI agent use the BlenderMCP server?
- Use it when a workflow needs live access to a Blender scene for prompt-assisted modeling, object manipulation, material changes, scene layout, lighting, camera setup, asset placement, or other authorized 3D creation tasks.
- What does BlenderMCP add to an AI agent's capabilities?
- It gives the agent structured tools for inspecting the current Blender scene and applying changes through the Blender add-on, allowing the agent to create, modify, and organize 3D content instead of only providing written instructions.
- What can an AI agent access or manage through BlenderMCP?
- The agent can inspect scenes and objects, create or delete geometry, update transforms, materials, colors, lighting, and cameras, execute Blender Python, and optionally retrieve external assets or generate models through supported third-party integrations.
- How is authentication configured for BlenderMCP?
- Core local Blender access does not require an API key. The MCP server connects to the enabled Blender add-on over a local socket, with BLENDER_HOST and BLENDER_PORT controlling the target. Optional services such as Hyper3D may require separate credentials or account access.
- Which transport should be used for BlenderMCP?
- Use the documented local stdio transport launched with uvx and the blender-mcp package. The server then communicates with the Blender add-on over its socket connection. The maintained documentation does not define a provider-hosted Streamable HTTP or SSE endpoint.