blender-compact-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUBMED_EMAIL | Yes | Your email address required by PubMed | |
| PUBMED_API_KEY | No | API key for higher rate limits (optional) |
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 |
|---|---|
| inspectB | Read a bounded scene summary; pass names for detailed object properties. |
| discoverB | List operation summaries, or fetch one operation's arguments. |
| executeA | Execute up to 100 {'op': name, ...arguments} steps. Returns counts/errors, not full scene data. dry_run checks syntax/permissions only. Runtime failures are partial, not transactional. |
| captureA | PNG preview (64..1024): camera render or viewport (requires interactive 3D View). |
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 4 tools
Each tool targets a clear, distinct concern: inspect reads scene state, discover exposes operation metadata, capture produces visual output, and execute runs operations. There is no meaningful overlap that would cause an agent to select the wrong tool.
All four tool names are single imperative verbs (inspect, discover, capture, execute), following a consistent and predictable style. The naming makes the toolset easy to scan and matches the compact design.
Four tools is well-scoped for a compact Blender MCP server: read, discover, execute, and visualize are all core capabilities with no filler. The count fits comfortably in the ideal 3-15 range.
The toolset forms a complete workflow for controlling Blender: discover what operations exist, execute them, inspect the resulting scene, and capture a preview. Any remaining limitations are documented runtime behavior rather than missing lifecycle coverage.