BlenderMCP

BlenderMCP bridges Claude and Blender's Python API, letting you script 3D scenes through conversation. You can create primitives, move objects, adjust materials, set up lights, and trigger renders without opening Blender's UI. The server exposes a handful of tools: execute arbitrary Python in Blender's context, create meshes, manipulate transforms, and handle basic scene operations. It's genuinely useful if you're prototyping 3D layouts or need to batch-generate variations of a scene. I've used it to set up lighting rigs from text descriptions and to position a dozen objects in a grid without clicking through Blender's interface. The workflow is straightforward: describe what you want, Claude writes the bpy commands, BlenderMCP runs them. Where it shines is repetitive setup work. If you're placing fifty cubes in a Fibonacci spiral or need to test ten material combinations, conversational scripting beats manual clicking. The quirks are real, though. You're still writing Python under the hood, so Claude needs to know Blender's API conventions. If it hallucinates a method name or gets the transform syntax wrong, you'll get cryptic errors. The server doesn't validate commands before sending them to Blender, so a typo can crash your scene state. There's no undo exposed through the MCP layer, which means you're leaning on Blender's built-in history or restarting the server. Render output paths and file handling aren't abstracted, so you'll specify absolute paths in your prompts. If you're a Blender power user who lives in Python anyway, this is a natural fit. If you're learning 3D and don't know bpy, you'll spend time debugging Claude's guesses. The server assumes Blender is already running with the MCP script loaded, which adds a setup step most MCPs skip. It's not a magic 3D generator, it's a remote control for Blender's scripting layer. That's powerful in the right hands, but it won't teach you 3D fundamentals.