blender-mcp
Blender MCP expert for scene inspection, Python scripting, GLTF export, and material/animation extraction. Activate when: (1) using Blender MCP tools (get_scene_info, execute_python, screenshot, etc.), (2) writing Blender Python scripts for extraction or manipulation, (3) exporting scenes to GLTF/GLB for web (Three.js, R3F), (4) debugging material or texture export losses, (5) optimizing GLB files with gltf-transform, (6) using asset integrations (PolyHaven, Sketchfab, Hyper3D Rodin, Hunyuan3D).
Security Assessment
About blender-mcp
blender-mcp is an expert-guidance skill for driving Blender through its MCP integration to inspect scenes, script with the Python `bpy` API, export to GLTF/GLB, and extract or debug materials and animations. It solves the practical pain of getting a Blender scene cleanly into a web 3D pipeline (Three.js, React Three Fiber) — where materials, textures, and modifiers silently degrade on export — by encoding the gotchas and the working order of operations.
The skill lays out tool selection (structured MCP tools like `get_scene_info` and `screenshot` for quick inspection, `execute_python` for non-trivial hierarchy traversal and material extraction, and headless CLI for exports that would otherwise time out the MCP server), a health-check-first workflow, and a complete linear export pipeline with ready-to-run Python for extracting the object hierarchy and auditing materials before committing to an export. Bundled references catalogue MCP/GLTF/`bpy` error causes and fixes, a texture-optimization pipeline using gltf-transform (resize, webp, draco applied as discrete steps rather than the destructive `optimize` shortcut), a material-export survival matrix (which Blender features reach GLTF and which must be baked or patched at runtime), GLTF name-mapping quirks, and asset integrations such as PolyHaven, Sketchfab, Hyper3D Rodin, and Hunyuan3D.
It targets 3D artists and web developers moving Blender content to real-time web rendering who hit export losses, oversized GLB files, or missing textures. It is a knowledge-and-workflow skill for legitimate content creation and debugging; the only notable behavior is executing user-directed Python inside Blender and running local Blender/gltf-transform CLI commands as part of a normal asset pipeline.
FAQ
When should I use execute_python versus the structured MCP tools?
Use structured tools like `get_scene_info` and `screenshot` for quick inspection, and `execute_python` for anything non-trivial — hierarchy traversal, material extraction, animation baking, or bulk operations — since it gives full `bpy` API access.
Why export GLTF via headless CLI instead of the MCP server?
The MCP server times out on export operations (roughly 15–30 seconds), so exports should run via `blender --background file.blend --python-expr "..."` on the CLI.
What is the recommended first step?
A health check: confirm the connection with `get_scene_info` (default port 9876), verify Python with a simple print via `execute_python`, and confirm viewport capture with `screenshot` before doing anything else.
Which Blender material features survive GLTF export?
Flat roughness/metallic values, image textures, baked normal maps, alpha, and emission export cleanly; procedural Noise textures, Color Ramp remapping, and bump-from-noise do not and must be baked to texture or patched at runtime.
How should textures be optimized without corrupting the mesh?
Avoid `gltf-transform optimize` (which includes simplify and can destroy the mesh); apply individual steps in order — resize, then webp, then draco — and apply Draco only once as the final step.
Install blender-mcp
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
vladmdgolam/agent-skills