blender-mcp-master
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_blender_skillB | Return the Blender MCP Master agent skill instructions (SKILL.md). |
| list_blender_resourcesA | List the skill reference guides and reusable Blender Python scripts bundled with this package. |
| get_blender_referenceA | Read one bundled modeling reference guide by exact filename. |
| get_blender_reference_outlineA | List only section headings and their line numbers from one guide. Low-context alternative to reading the full document. |
| get_blender_reference_excerptA | Read only a bounded line window from a reference. Returns continuation line; use before requesting full text. |
| get_blender_scriptA | Return one reusable Blender Python script by exact filename. Review its configuration and safety notes before execution. |
| get_blender_mcp_setupB | Explain how this skill/resource server relates to a separate MCP server that controls a live Blender session. |
| plan_blender_workflowC | Recommend minimal on-demand guides and unanswered design topics without touching Blender. |
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 8 tools
Each tool has a distinct role: skill instructions, resource listing, reference reading, outline, excerpt, script retrieval, setup explanation, and workflow planning. The three reference-reading tools (get_blender_reference, get_blender_reference_outline, get_blender_reference_excerpt) operate on the same documents at different granularities, which could cause some misselection, but the descriptions clearly delineate low-context vs. bounded-window vs. full-read use cases.
All tools follow a uniform snake_case verb_noun pattern scoped by the domain (get_blender_*, list_blender_*, plan_blender_workflow). No mixed conventions or abbreviation drift, making intent predictable from the name alone.
Eight tools is well-scoped for a read-only skill/resource server with no redundancy. Every tool maps to a distinct access pattern (metadata, full read, outline, excerpt, script, setup, planning) and none feels padded.
The read-only resource surface is largely complete: discovery, granular reading, scripts, setup context, and planning are all covered. The main gap is a search/lookup tool to find which reference covers a topic without first listing files; otherwise no dead ends for the stated purpose.