MCP server · Blender 4.2 – 5.2 · verified on 5.2.1
It builds the scene. Then it looks.
192 tools that let Claude, Cursor or any MCP client model, texture, light, animate, simulate and render inside a running Blender — pull free assets from Poly Haven — and see the render before it says it is done.
One-time purchase · macOS, Windows & Linux · Node 18+
By the numbers
Tested in a real Blender session.
The release was exercised in Blender 5.2.1 across modelling, materials, lighting, animation, physics, rendering and import/export. Results were checked from returned data and renders.
The part that matters
A monkey was lying face-down. Nothing in the JSON said so.
During development every call reported success — objects created, materials assigned, lights placed. Then the first render came back and Suzanne was flat on her face. That is the whole argument for returning images, told in one scene.
22 calls, all "ok"
Pedestal, monkey, halo, three materials, three-point rig, camera, DOF. Every response green.
Face-down
bx_render returned the image. The model saw the mesh lying flat and knew the numbers had not told the truth.
Worse
A 90° X rotation buried her face in the pedestal. The render showed that too.
Upright, facing camera
Diagnosed as a Z-axis problem, rotated 45°, re-rendered, confirmed. The loop converged because it could see.
Catalogue
Thirty-five categories. Five tools at connect.
Every tool's schema costs context before the model reads your first word. 192 of them would
cost about 35,000 tokens, so they load lazily: the core 5 are visible at connect and the model
calls bx_enable_tools for the categories the task needs. The client's tool list
refreshes on its own.
The model loads what it needs mid-conversation. Prefer to pre-load, or use a client that ignores list changes? Two environment variables cover it.
BLENDER_MCP_CATEGORIES=mesh,materials # pre-load BLENDER_MCP_EAGER=1 # load all 192
Blender 5.x
Three API breaks the docs did not mention.
Each one took down a whole category of tools on first run. The server now includes compatibility paths for the affected 4.2 and 5.2 APIs.
Removed in 5.x. Slotted actions moved F-curves to layers[].strips[].channelbags[].fcurves. Every animation tool failed at once. A helper now walks whichever structure the build has.
Compositing rebuilt. The compositor is now a node group on scene.compositing_node_group, the Composite output node is gone, and Glare moved every setting onto input sockets. The old node name is accepted as an alias so 4.x-era instructions still work.
Needs a 3D viewport. Blender's own operator calls one that fails outside a UI context. The simulation is sampled manually instead — record every frame, strip the rigid bodies, then write the keys.
Safety layer
Let the AI work. Keep the undo.
No other Blender MCP ships this: a dedicated safety category that checkpoints the whole scene, lists every change the AI made field by field, and rolls everything back in one call. Experiment freely — nothing is irreversible.
Checkpoint everything. A named, restorable copy of the full scene before risky work — written to disk, so it survives crashes and restarts.
See every change. Compare against a captured baseline: objects added, removed or modified, with before/after values for transforms, materials, visibility and animation.
Roll back in one call. Restore any named snapshot — the whole scene returns to that exact state, whatever the AI (or you) did afterwards.
Scope, stated plainly
What v1.0 covers, and what it does not.
You should know the gaps before you pay, not after. Most of what is missing is still reachable through bx_exec_python; it simply has no validated tool yet.
In v1.0
- Modelling: primitives, extrude, inset, bisect, booleans, 70 modifier types
- Materials, shader nodes, image textures, vertex colours, UV unwrap and bake
- Lighting rigs, HDRI, cameras with DOF, framing
- Keyframes, shape keys, drivers, constraints, IK
- NLA tracks and strips, plus video, audio, images and transitions in the sequencer
- Scene audits, product stages, turntables, game-asset preparation and project packing
- Rigging, automatic weights, rig diagnostics
- Rigid body, cloth, soft body, force fields, particles, hair
- Curves, geometry nodes presets, compositor presets
- Render to image, animation render, a whole camera set in one call, import/export in 7 formats
- Deterministic texture painting: generated canvases with painted shapes in UV space
- Poly Haven: free HDRIs, PBR textures and models, applied from the chat
Not in v1.0
- Grease Pencil authoring
- Sculpt brush strokes (the tool prepares sculpt mode for a human)
- Freehand texture painting strokes (deterministic paint shapes ARE included)
- Motion tracking
- Fluid and smoke simulation
Setup
Five minutes. No compiler.
Install the add-on
Run the installer for your platform, then enable the add-on from Blender's Preferences (Install from Disk). It also prints your MCP client config.
./install-macos.sh # macOS ./install-linux.sh # Linux install-windows.bat # Windows
Register the server
One line. There is no npm install — the server ships as a single bundled file that needs only Node 18.
claude mcp add blender-ultra -- node "/path/to/BlenderMCPUltra/server/dist/server.js"
Open Blender and ask
The kernel starts listening when Blender starts. Ask your assistant to run bx_status; it reports the Blender version it is talking to.
Preview only: checkout is in sandbox. Requires Blender, Node.js 18+ and a configured MCP client. AI usage costs are separate. Setup guide · Verified demo
Pricing
Buy once. Keep it.
- All 192 tools, nothing gated — including the safety layer
- Lifetime updates across 1.x
- Core tools run locally; Poly Haven downloads are optional
- No licence server or telemetry
- Unlimited personal and commercial projects
- Verified on macOS; Windows and Linux installation testing pending
PayPal worldwide · Pix, OXXO, tarjetas locales vía dLocal Go
Why only 5 tools when I connect?
Because 192 schemas would eat about 35,000 tokens of context before you said anything. Ask for a category — "load physics" — and it appears; the server lists them all in its instructions.
Which Blender versions?
The compatibility target is 4.2 through 5.2. This release was verified in Blender 5.2.1; use the included status tool after installing on another version.
Why two licences in the package?
The add-on uses Blender's Python API and is distributed under GPL. The bundled MCP server is distributed under its own proprietary licence.
Does it need Cycles?
No. It renders with whatever engine the scene uses and reports which engines the build offers. EEVEE is the default; Cycles is used for baking when present.
What if a tool does not cover my case?
bx_exec_python runs anything on Blender's main thread with bpy in scope, with structured results and real tracebacks.
Team use?
One licence per developer. Studios buy one seat each — get in touch for volume terms.