Blender MCP
Drive a live Blender session from Claude via the Model Context Protocol.
About
Blender MCP (now published as mcp-for-blender) is the community-standard bridge letting LLMs control Blender 3D through the Model Context Protocol. A Blender addon exposes a socket server inside the app while a stdio MCP server (installed via uvx) gives Claude Code, Claude Desktop, Cursor, VS Code, Codex or OpenCode around 36 tools: scene and object inspection, viewport screenshots, arbitrary bpy code execution, material control, and GLB/FBX export — plus asset integrations for Poly Haven, Sketchfab, Hyper3D Rodin and Hunyuan3D.
With roughly 29,000 GitHub stars it is the de-facto standard for agentic 3D work, and a whole ecosystem of skills builds on it. Setup is two halves that must both run: the addon inside Blender listening on port 9876, and the MCP server launched by your client. Note that execute_blender_code runs arbitrary Python with your user permissions, so checkpoint .blend files before destructive operations; telemetry is anonymous and opt-out.
What it can do
- Natural-language Blender scene control
- bpy code execution from the agent
- Viewport screenshot capture
- Poly Haven, Sketchfab and AI 3D asset integration
- Material and object manipulation
- GLB/FBX scene export
Setup
Install uv, add the MCP server to your client (e.g. claude mcp add blender uvx mcp-for-blender), then install the addon in Blender via uvx mcp-for-blender install-addon.
Prerequisites
Blender 3.0+, Python 3.10+ (via uv), and an MCP client such as Claude Code or Cursor.
Use cases
Works with
Trust score — 9/10
Scored 9/10 (verified tier, metrics-v1). Evidence: Verified via vendor site/docs/GitHub and reputable coverage, wave 64; Trending score 90/100 from researcher assessment.
★ 29,400 GitHub stars
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.