Claude's Blender connector: the complete step-by-step guide

On this page · 11 sections▾

The announcement
What it actually is
Watch it in action
Setup, step-by-step
8 things you can do with it
Official vs. community
The 9-connector cohort
Gotchas (5 that bite)
Who this is for
FAQ
Sources

The announcement

Here’s the post that started it all — a single tweet from @claudeai framing the entire creative-tools push around three concrete Blender verbs: debug, build, batch.

Claude now connects to the tools creative professionals already use.

With the new Blender connector, you can debug a scene, build new tools, or batch-apply changes across every object, directly from Claude. pic.twitter.com/Kc3cBHTNpV
— Claude (@claudeai) April 28, 2026

The launch wasn’t Blender-only. Anthropic shipped nine connectors at once — Adobe (50+ Creative Cloud apps), Affinity by Canva, Ableton Live, Splice, SketchUp, Autodesk Fusion, Resolume Arena, Resolume Wire, and Blender — framed in a longer post called “Claude for Creative Work.” Blender is the one we’re here for: it’s the only fully open-source partner in the cohort, and the only one where Anthropic also became a financial patron of the upstream project (Anthropic joined the Blender Development Fund alongside the connector release).

What the connector actually is

Stripped of marketing copy, the Blender connector is one thing: an MCP (Model Context Protocol) server that exposes Blender’s Python API — bpy — as a set of tools Claude can call. When you turn it on, Claude gains the ability to:

Read the scene graph — every object, modifier, material, light, camera, render setting, and collection.
Write arbitrary Python that runs inside the live Blender process — so it can create, modify, or delete anything bpy can reach.
Observe — capture viewport screenshots and reason about what the scene actually looks like, not just what its data says.
Extend — register new operators, panels, and shortcuts that persist as if you’d written a permanent Blender addon.

That last point is the one most people miss on first read. The Anthropic announcement specifically calls out “build new tools” — not “run a script.” The connector can write a fresh operator, wire it into a sidebar panel, and from then on you click a button instead of asking Claude. The AI is a build-step, not a run-time dependency.

Why MCP and not a plain plugin? Because once it speaks MCP, it speaks every MCP host. Cursor, Cline, Continue, VS Code Copilot agents, the Claude Agent SDK, and any future client all get to drive Blender through the same surface. Blender’s blog post on the launch was explicit about that — the connector is open-source-aligned because it works for any LLM, not just Claude.

Watch it in action

Sixty seconds of footage is worth more than any feature list. This community Short demos the typical flow: prompt in, scene changes out, viewport screenshot back, refine.

Note: that demo predates the official April 2026 connector and uses the community blender-mcp package. The feel is identical — same MCP plumbing, same bpy Python on the other end — but the official path skips the manual uvx install, which we’ll cover next.

Setup, step-by-step

Two paths depending on which connector you’re running. Pick one. Don’t run both at once — Blender only accepts one MCP client per session, and the second one will silently fail to connect.

Path A: Official connector (recommended)

For Claude Desktop or Claude.ai users on a current build. The connector ships through Anthropic’s connector directory, so installation is a toggle, not a config edit.

Update Blender to 4.5 LTS (or any version 3.0+). The connector relies on stable parts of bpy introduced in 3.0.
Open Claude Desktop, then Settings → Connectors → Browse.
Find “Blender” in the connector list (it sits near SketchUp and Fusion in the creative section). Click Enable.
Approve the local launch. Claude will prompt the OS to run the local helper and connect to your running Blender instance.
Open Blender and confirm the BlenderMCP panel is visible in the 3D View sidebar (press N to toggle the sidebar). The status pill should read Connected.

That’s the entire flow. From this point on, every Claude conversation has Blender available as a tool, and you can revoke it from the same Connectors panel.

Path B: Community blender-mcp (for non-Claude clients)

Use this if you want Blender hooked up to Cursor, Cline, Continue, or any other MCP host. It’s the path the YouTube short above demonstrates.

Install uv (the fast Python package runner): brew install uv on macOS or the platform installer from astral.sh/uv.
Add to your client’s MCP config — for Claude Desktop, that’s Settings → Developer → Edit Config:
```
{
  "mcpServers": {
    "blender": {
      "command": "uvx",
      "args": ["blender-mcp"]
    }
  }
}
```
Install the Blender addon. Download addon.py from the ahujasid/blender-mcp GitHub repo, then in Blender: Edit → Preferences → Add-ons → Install, select the file, and tick the checkbox to enable it.
Connect from Blender: open the 3D View sidebar (N), find the BlenderMCP tab, optionally enable Poly Haven for free assets, then click Connect to Claude.
Restart your MCP client so it discovers the new server.

The community path takes longer, but it’s the right pick if you want Hyper3D Rodin / Hunyuan3D text-to-3D generation, Poly Haven asset search, or Sketchfab imports — those are all features layered on top of the base MCP surface that the community version ships pre-wired.

8 things you can do with it

These are real Blender tasks, ordered roughly from “saves you five minutes” to “saves you an afternoon.” Each is a single Claude prompt with the rough flavor of what gets generated. Treat them as recipes you can paste, not as a complete reference.

1. Inspect the scene before you touch anything

The single most underrated use. Before you delete or batch anything, ask Claude to walk the scene graph and summarize. It catches the “wait, that mesh has nine modifiers stacked” surprises before they bite.

Prompt: Walk the current scene. List every collection, the object count per collection, any objects without materials, anything with a broken (red-text) modifier, and the active camera’s framing.

2. Debug a black render in 30 seconds

The classic 2 a.m. problem. Black render, sun lamp on, world set, what’s wrong? Claude reads the render settings, checks for a missing world background, an off camera, a hidden light layer, or a clip-distance issue, then proposes the fix.

Prompt: My render is fully black. Inspect render settings, world, lights, camera, view-layer visibility, and report the most likely cause. If you can fix it without moving anything else, do it.

3. Batch-apply a modifier across hundreds of objects

The flagship use case from the launch tweet. Adding a subdivision modifier to 400 selected objects through the GUI takes minutes; Claude does it in one prompt. Same pattern works for bevel, mirror, array, smooth shading, custom normals, you name it.

Prompt: For every mesh object in the “props” collection: add a 2-level subdivision surface modifier, set shading to smooth, and lock the modifier in the viewport. Skip anything that already has a subsurf.

4. Generate a one-off operator and pin it to the toolbar

The “build new tools” verb from the announcement. Tell Claude what the tool does in plain English, and it writes a proper bpy.types.Operator, registers it, and adds it to a sidebar panel. The operator survives the file save and behaves like any other addon button.

Prompt: Build a Blender operator called “Snap Selected To Floor” that drops every selected object to Z=0 along their lowest bounding-box vertex. Add it to the View tab in the sidebar and bind it to Shift+S Shift+Z.

5. Audit material slots across the whole project

The kind of thing you’d normally write a 40-line script for. Instead, Claude reads every material on every object, groups them, finds the duplicates with slightly different names (“Wood”, “Wood.001”, “wood_old”), and proposes a merge plan.

Prompt: Audit materials across the file. Find duplicates (similar names or identical node trees), report the consolidation plan, then ask me to confirm before merging. Show file-size delta.

6. Rename and reorganize a messy outliner

The “Cube.001 through Cube.847” horror. Claude clusters by mesh similarity, position, or material, suggests a naming scheme, and applies it across collections. Pairs well with material audits.

Prompt: Cluster every object in the scene by their primary material, rename each cluster as {material}_{index:03d}, and move them into per-material collections. Don’t touch cameras, lights, or armatures.

7. Set up a render queue with three quality tiers

Preview, draft, and final at three different sample counts and resolutions, queued to render sequentially with different output paths. Claude writes the script, runs it, and reports back when each pass finishes.

Prompt: Queue three Cycles renders of the current scene at: 480p/64 samples, 1080p/256 samples, 4K/1024 samples. Save each to ~/renders/{tier}.png. Report progress after each.

8. Bake an entire export pipeline into a permanent script

The endgame. Once you’ve iterated three or four times on a workflow, ask Claude to wrap the whole thing as a permanent operator in your startup directory. You stop paying token cost for that workflow forever.

Prompt: Wrap the last three things you did into a single operator called EXPORT_OT_clean_glb: clean the scene, apply all modifiers on a copy, export to GLB at the path I pass in, report stats. Save it to my Blender startup folder.

Official connector vs. community blender-mcp

Both speak MCP. Both drive bpy. Choose based on what you actually want to wire it into.

Dimension	Official (April 2026)	Community (ahujasid/blender-mcp)
Built by	Blender Foundation devs	Independent maintainer (ahujasid)
Install path	One-click toggle in Claude	`uvx blender-mcp` + addon.py
Works with non-Claude clients	Yes (it’s MCP)	Yes (it’s MCP)
Asset integrations	Core `bpy` only	Poly Haven, Sketchfab, Hyper3D, Hunyuan3D
Update cadence	Tied to Blender releases	Maintainer-driven, faster on new tools
Best when	You live in Claude and want zero friction	You want every bell and whistle, or non-Claude

The honest answer for most readers is: enable the official one in Claude Desktop, keep the community one bookmarked for the day you need text-to-3D or Poly Haven assets. They’re not mutually exclusive — just don’t run both against the same Blender instance at the same time.

The 9-connector cohort, in one breath

Blender lands inside a much bigger announcement. Here’s the full list and what each one is for, so you know which ones to enable alongside Blender for a multi-tool pipeline.

Adobe — 50+ Creative Cloud apps (Photoshop, Premiere, After Effects, Express). The texture-and-comp half of any Blender pipeline.
Affinity by Canva — batch image ops, layer renaming, file-format conversion. Cheaper, scriptable alternative to Photoshop for batch work.
Ableton Live + Push — primarily product-documentation tutoring and patch design. Useful if your Blender work is for game audio or motion graphics.
Splice — royalty-free sample search. Pairs with Ableton.
SketchUp — conversational starting 3D model. The right tool when you want a building blocked out before you finish in Blender.
Autodesk Fusion — parametric CAD. Use this when the part has tolerances; switch to Blender when it has personality.
Resolume Arena — live VJ control.
Resolume Wire — node-based visual patching for live sets.
Blender — the only fully open-source partner, the only one Anthropic financially sponsors via the Development Fund.

Gotchas (5 that bite)

Pulled from the launch threads, the community blender-mcp issue tracker, and the first wave of YouTube walkthroughs. In rough order of how often they ruin a session.

Two clients, one Blender

Blender accepts a single MCP client per session. If you have Claude Desktop and Cursor both configured for blender-mcp, the second one to connect silently fails. Pick one per session, or quit one before starting the other.

First command after launch sometimes hangs

The MCP handshake races against Blender's startup script. The fix is to send a trivial 'list collections' first; the second prompt always works. Filed against ahujasid/blender-mcp; the official connector has the same race in its early builds.

Claude can run any Python it wants

There is no sandbox. The connector is doing what it says on the tin — driving bpy. Save before destructive operations (apply-all, baking, mass deletes), keep a backup file, and review the script when the change feels large. The convenience comes from trusting it.

Viewport screenshots aren't free

Each screenshot is a real image upload to Claude. Three or four per turn is fine; thirty across a session and you'll feel it in token bills. Disable the auto-capture toggle for routine batch jobs where you don't actually need to see the result.

Big scenes can time out the tool call

Anything over ~50k objects starts to hit MCP's default tool-call timeout. Solution: chunk the prompt ('process collection A first, then B'), or ask Claude to write the script, save it, and run it via Blender's text editor instead of through the connector.

Who this is actually for

Four audiences map cleanly onto the use cases above.

Indie 3D artists — the batch and cleanup verbs (use cases 3, 5, 6) save the most time. You do the creative work; Claude handles the per-object drudgery.
Technical directors — use case 4 (build a custom operator) and use case 8 (bake into a permanent script) are the productivity wins. Treat the connector as a fast addon-prototyping tool.
Indie game developers — the export pipeline (use case 7, 8) plus material auditing (5) matter most. Combined with the Adobe connector for textures and the Splice/Ableton pair for audio, it’s a one-engineer shop now.
VFX and arch-viz — debugging (1, 2) and render-tier queueing (7) compress iteration time. The work is still yours; the bookkeeping isn’t.

The audience the connector doesn’t really serve: students learning Blender from scratch. Driving the viewport via prompt is a great accelerator if you already know the menus, and a great way to short-circuit learning if you don’t. Lean on the Blender Foundation’s free Donut tutorial first.

FAQ

Is the Blender connector official, or is it the community blender-mcp?

Both exist. The official Blender connector announced on April 28, 2026 was built by the Blender developers themselves, ships through Claude's connector directory, and is the path Anthropic recommends. The longstanding community project — ahujasid/blender-mcp — pioneered the pattern, still works, and is the install you reach for if you want to run Blender against Cursor, VS Code, or any non-Claude MCP client. Both speak MCP, both drive Blender's Python API, but the official one is the one-click toggle.

Do I need to write any Python to use it?

No. The whole point is natural-language access to Blender's Python API (bpy). You describe what you want — 'apply a 2-level subdivision and smooth shading to all meshes', 'fix the black render', 'snap every prop to the grid' — and Claude writes the Python, runs it inside Blender, and reports back. You only touch Python yourself when you want to lift one of Claude's scripts into a permanent operator or addon.

Which Blender versions does it support?

Blender 3.0 and later, with Blender 4.5 LTS as the recommended baseline. The connector relies on stable parts of bpy that haven't shifted between recent releases. If you're still on 2.9x for a legacy pipeline, the connector won't load — that's a Blender API limit, not a Claude one.

Can it generate 3D models from scratch?

By itself, no — the connector drives Blender, it doesn't model for you. But the community blender-mcp pairs with Hyper3D Rodin and Tencent's Hunyuan3D for text-to-3D, and the official connector composes naturally with Anthropic's other April 2026 partners — SketchUp (conversational starting model) and Autodesk Fusion (parametric CAD). The shape Claude is best at: take a generated or imported asset, then tweak, light, and frame it with the connector.

Is my Blender file safe? The connector executes arbitrary Python.

Treat it the same way you'd treat any addon that exposes 'run script.' Save before invoking large operations, work in a copy when you're experimenting, and review the script Claude proposes when the change is destructive (deletes, applies modifiers, or bakes data). The connector doesn't sandbox the Python it runs — that's by design, because half the use cases require full bpy access.

How is this different from generative AI tools like Stable Diffusion in Blender?

Stable Diffusion in Blender generates pixels — a textured render, a procedural material map. The Claude connector generates instructions — Python that builds, edits, or interrogates the scene itself. The two compose: a typical pro session uses the connector to set up 12 props in 4 lighting passes, then a diffusion addon to texture the hero asset. Different layers of the pipeline.

Does it work with Eevee, Cycles, or only viewport?

Both render engines, plus the viewport. Claude can read render settings, switch engines, change samples, and trigger renders to disk. The viewport is where most debugging happens because the connector can capture a screenshot and reason about what's visibly wrong (occluded camera, missing world, NaN normals).

Can multiple people drive the same Blender session?

No, and that's a hard limit. The MCP server expects one client at a time — running Claude Desktop and Cursor against the same Blender instance is the most common way to break it. If you want collaborative drive-by-AI, your team needs separate Blender instances or a queue.

Where do the official docs live?

Anthropic's launch post is at anthropic.com/news/claude-for-creative-work — that's the canonical pointer. The connector itself is enabled from inside Claude (Settings → Connectors → Blender) on the desktop app. For the community version, the source of truth is the ahujasid/blender-mcp GitHub repo, which is what most existing tutorials and YouTube videos demonstrate.

Sources

Primary

Coverage

Internal