MCP for Blender

MCP for Blender connects Blender to an LLM through the Model Context Protocol so that a model can build, edit, and inspect 3D scenes from a chat prompt. It is a third-party integration, not made by Blender, and has two parts: a Blender addon that runs a socket server inside Blender to receive and execute commands, and a Python MCP server that implements the protocol and relays an agent's tool calls to that addon over a JSON-over-TCP exchange.

The model does most of the work by writing Blender Python itself for modeling, layout, materials, animation, rigging, and retopology, and the server adds nine tools for what Python alone cannot do. The look tool returns the viewport, camera, an auto-framed multi-angle sheet, or an animation strip in solid, material, rendered, wireframe, or X-ray mode so the model checks its own output. A scene summary tool lists one line per object with chosen fields such as placement, materials, topology, and weights. Asset tools search and import Poly Haven HDRIs, textures, and models, Sketchfab models, and Poly Pizza low-poly models, writing source, license, and attribution data onto the imported objects as custom properties. A generate tool creates and imports an AI-generated model through Tripo, Hunyuan3D, or Hyper3D Rodin, with a paid Premium tier that supplies those generators without your own API keys.

A one-command setup detects the MCP clients on the machine (Claude Desktop, Claude Code, Codex, Cursor, VS Code, Devin Desktop/Windsurf, OpenCode, and Antigravity), adds a blender entry to each chosen configuration while backing up the originals, and installs and enables the addon. A Codex plugin adds a live viewport inline in the chat, thumbnail pickers for the asset libraries, and mentions for scene objects, materials, and collections. The server can also run in a container while Blender stays on the host, and several Blender instances can be driven side by side by giving each its own socket.

The code-execution tool runs arbitrary Python inside a live Blender session, so an optional safe mode validates each script before it runs and blocks file, process, and network access and persistent code, returning the reason to the model for a retry. The addon's socket has no authentication or encryption and is meant to stay on the local machine. Telemetry defaults to a minimal anonymous usage record, with prompts, generated code, screenshots, and scene data collected only after an explicit opt-in, and can be switched off entirely.