MCP for Blender

MCP for Blender connects a Blender addon to any LLM client that speaks the Model Context Protocol (MCP), such as Claude Desktop, Claude Code, Cursor, or Codex. It's built for developers and 3D artists who want to drive Blender through natural-language prompts instead of clicking through menus, and for anyone experimenting with AI-assisted modeling workflows. The project was formerly published as blender-mcp on PyPI and is now mcp-for-blender; old configs keep working unchanged.

The system has two parts: a Blender addon (addon.py) that opens a local socket server inside Blender, and a Python MCP server (src/blender_mcp/server.py) that implements MCP and talks to that addon. Your LLM client launches the MCP server, which forwards commands to Blender over the socket.

Key features

• Two-way communication: a socket-based bridge lets an LLM send commands to Blender and read results back.
• Object manipulation: create, modify, and delete 3D objects directly from prompts.
• Material control: apply and adjust materials and colors on objects.
• Scene inspection: pull detailed information about the current Blender scene for context-aware edits.
• Arbitrary code execution: run Python code inside Blender on request, useful for scripted or repetitive tasks.
• Asset and model generation: pull in Poly Haven assets, Sketchfab models, Poly Pizza low-poly models, or generate models with Hyper3D Rodin and Hunyuan3D.
• Safe mode: an optional setting that screens scripts before execution and blocks risky operations like file access, network calls, or launching other programs, while normal modeling, materials, and rendering still work.
• Multi-instance support: run several Blender instances side by side using different ports, each with its own MCP client entry.

Ideal use cases

This fits well if you already use Blender and want an LLM to handle repetitive modeling, scene setup, or material tweaks through conversation instead of manual UI work. It's also useful for quickly pulling in assets from Poly Haven, Sketchfab, or Poly Pizza, or generating base meshes with Hyper3D Rodin / Hunyuan3D and then refining them by hand. Developers building on MCP-compatible clients (Claude Desktop, Claude Code, Cursor, VS Code, Codex, OpenCode, Antigravity) get a ready-made Blender integration instead of writing one from scratch.

It's not a good fit if you need remote or multi-user access without extra hardening: the addon's socket server has no authentication or encryption by default, so exposing it beyond localhost is a real risk. It's also not meant for production pipelines that require deterministic, repeatable output. Since the LLM can run arbitrary Python inside Blender (unless safe mode is on), it's not appropriate for untrusted environments or shared machines without care.

Installation

Prerequisites: Blender 3.0+, Python 3.10+, and the uv package manager (install via the official installer, not pip install uv).

1. Install uv:

# macOS
brew install uv
# Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# Windows
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"

2. Point your MCP client at the server. For Claude Desktop, edit claude_desktop_config.json:

{
    "mcpServers": {
        "blender": {
            "command": "uvx",
            "args": ["mcp-for-blender"]
        }
    }
}

For Claude Code:

claude mcp add blender uvx mcp-for-blender

For Codex:

codex mcp add blender -- uvx mcp-for-blender

Cursor, VS Code, OpenCode, and Antigravity have their own equivalent config entries or one-click install links documented in the README.

3. Install the Blender addon:

uvx mcp-for-blender install-addon

Then in Blender, go to Edit → Preferences → Add-ons and enable Interface: MCP for Blender.

4. Connect: in Blender's 3D viewport, press N, open the MCP for Blender tab, and click Start MCP Server. Only run one instance of the MCP server at a time (either in Cursor or Claude Desktop, not both), unless you deliberately configure multiple ports for multiple Blender instances.

Alternatives to uvx include pipx install mcp-for-blender for locked-down machines, or running the server in Docker with docker build -t mcp-for-blender . and connecting via BLENDER_HOST=host.docker.internal (macOS/Windows) or --network=host (Linux).