Blender-Mind-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| blender_create_primitiveB | Creates a 3D procedural primitive (cube, sphere, cylinder, torus, plane, cone, monkey) in the 3D scene. |
| blender_apply_modifierB | Attaches and configures a procedural modifier (subsurf, bevel, boolean, mirror, array, solidify) to a target mesh object. |
| blender_procedural_materialA | Creates a physically-based (PBR Principled BSDF) material with metallic, roughness, glass transmission, or emission, and binds it to an object. |
| blender_setup_lightingA | Creates or configures a 3D light source (Sun, Point, Spot, Area) in the scene with position, energy wattage, and color tint. |
| blender_setup_cameraB | Creates and positions the scene camera with look-at target tracking and focal length lens adjustments. |
| blender_capture_viewportA | Captures an instantaneous OpenGL screenshot of the 3D viewport and returns it as a Base64-encoded PNG image for multimodal visual inspection. |
| blender_export_assetA | Bakes and exports the current 3D scene into standard 3D formats (.glb, .gltf, .obj, .stl, .fbx). |
| blender_inspect_sceneB | Retrieves complete inspection metadata from the 3D scene, including all mesh objects, transform coordinates, polygon counts, vertex counts, materials, and modifier stacks. |
| blender_execute_bpyA | Directly runs custom Blender Python (bpy) scripts with full error containment and return value capture. |
| blender_healthA | Reports connection status, detected Blender binary version, active simulation engine, and system readiness. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct aspect of 3D workflow: camera setup, primitive creation, modifiers, materials, lighting, viewport capture, export, scene inspection, custom scripting, and health check. There is no functional overlap that would cause an agent to misselect a tool.
Almost all tools follow a consistent 'blender_verb_noun' pattern (setup_camera, create_primitive, export_asset, inspect_scene). Two exceptions exist: 'blender_procedural_material' lacks a verb, and 'blender_health' is a noun-only name, but they are still recognizable and do not break the overall pattern significantly.
With 10 tools, the set is well-scoped for a Blender integration. It covers the essential actions for scene creation, modification, inspection, and export without overwhelming bloat. Each tool earns its place, and the count is optimal for the domain.
The tool set covers the full modeling workflow: creating primitives, applying modifiers, materials, lighting, camera, viewport capture, export, and scene inspection. Minor gaps exist, such as direct editing of transforms or deletion of objects, but these can be managed via the custom `blender_execute_bpy` tool, so the surface is largely complete for typical tasks.