Blender MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLENDER_MCP_PROJECT_ROOT | Yes | Absolute path to the project root containing .blend files and preview outputs. This is the security boundary for file access. | |
| BLENDER_MCP_BLENDER_EXECUTABLE | Yes | Absolute path to the Blender executable (e.g., /Applications/Blender.app/Contents/MacOS/Blender). |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_blender_statusA | Check whether the configured Blender and bundled adapter are available. |
| inspect_sceneA | Inspect a project-relative .blend file without modifying it. |
| render_previewB | Render a PNG preview to a project-relative output path. |
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 3 tools
Each tool has a clearly distinct purpose: checking environment status, inspecting a blend file, and rendering a preview. No two tools overlap in function.
All tool names follow a consistent verb_noun pattern (get_blender_status, inspect_scene, render_preview), making the intended action obvious.
Three tools is at the low end of the typical well-scoped range, but each serves a distinct function without redundancy. The count feels minimal rather than excessive.
The server lacks any tools for creating, editing, or saving Blender scenes, which are common operations for a Blender integration. The existing tools only cover a narrow inspect-and-render workflow, leaving significant gaps for general-purpose use.