When to use: You want a quick 3D scene mockup but don't want to learn Blender shortcuts.
Prerequisites
- Blender 3.0+ installed — Download from blender.org
- Blender MCP addon enabled — Edit > Preferences > Add-ons > Install from disk
Flow
-
Connect Claude to Blender
Open Blender. In the N-panel, click 'Connect to Claude'. Verify connection in chat by listing scene objects.✓ Copied
→ Empty scene listed (Cube, Camera, Light) confirming live connection
-
Compose the scene
Build a low-poly forest clearing: 5 trees in a circle, a campfire in the center, a sleeping bag nearby. Use simple geometry.✓ Copied
→ Objects appear in viewport in real time
-
Add atmosphere
Search PolyHaven for a sunset HDRI. Apply it. Then add a small fog volume above the ground.✓ Copied
→ Scene now has lit atmosphere; fog visible in render
Outcome: A prototype 3D scene built entirely through chat, ready for refinement.
Pitfalls
- Blender disconnects mid-session — Reconnect from the N-panel; the addon listens on a local socket
When to use: You need a unique prop and don't want to model from scratch or pay for marketplace assets.
Prerequisites
- Hyper3D rodin API key (free tier available) — Sign up at hyper3d.ai; set HYPER3D_RODIN_API_KEY
Flow
-
Generate from prompt
Generate a stylized treasure chest with iron bands using Hyper3D rodin. Import it at origin.✓ Copied
→ Generation job spins up; mesh imported when done (~30s)
-
Refine and re-import if needed
The mesh is too dense. Decimate to 5k tris and reimport.✓ Copied
→ Decimated mesh replaces original
Outcome: Custom 3D prop in scene, generated and tuned without leaving Claude.
Pitfalls
- Generation queue is busy on free tier — Retry with exponential backoff or upgrade tier
When to use: You need a tedious bulk action — rename hierarchy, retarget materials, batch UV unwrap.
Flow
-
Describe the operation
Every object starting with 'prop_' should be moved into a 'Props' collection and have its origin set to geometry center.✓ Copied
→ Claude writes the bpy snippet, asks to confirm before running
-
Run with safety net
Show me the script first. If it looks safe, execute. Otherwise revise.✓ Copied
→ Script visible; execution applied; report of how many objects affected
Outcome: Bulk scene operations done in seconds with full audit trail.
Pitfalls
- Bad script crashes Blender — Save before any bpy execution; the addon doesn't sandbox