Blender MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLENDER_MCP_CONFIG | Yes | Path to the config.json file for Blender MCP server |
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 |
|---|---|
| ping_blenderA | Check that Blender bridge is running and responding. |
| get_server_configA | Return MCP server config (bridge URL, export targets, Summit conventions). |
| scene_informationA | Scene summary: file path, frame range, object/armature/action counts. |
| list_objectsC | List objects. filter_type: ALL, MESH, ARMATURE, EMPTY, CURVE. |
| list_armaturesA | List armature objects in the scene. |
| list_bonesA | List bone names for an armature (pose or edit names). |
| list_actionsA | List all actions (animation clips) in the blend file. |
| get_object_transformB | Get location, rotation, and scale for an object. |
| create_actionB | Create a new empty action (animation clip) with the given name. |
| rename_actionB | Rename an existing action. |
| set_active_actionC | Assign an action to an armature for editing/playback. |
| set_frameC | Set the current scene frame. |
| set_bone_rotation_keyframeC | Insert a rotation keyframe (Euler XYZ radians) on a pose bone. |
| set_action_loop_modeC | Set action cycle mode: REPEAT, CLAMP, or PING_PONG. |
| export_gltfC | Export glTF/GLB. action_names limits exported animations (None = all). |
| export_to_summitC | Export to a configured Summit folder (see config export_targets). |
| validate_scene_scaleB | Validate unit scale: checks mesh height vs Summit infantry target (~1.6m). |
| validate_action_root_motionB | Warn if root bone has location keyframes (bad for in-place RTS locomotion). |
| create_summit_bobcatC | Build Bobcat V1 blockout (simple boxes, idle + harvest). |
| create_summit_bobcat_v2C | Build Bobcat V2 from RTS parts catalog (chunky Generals-style, idle + harvest). |
| create_summit_servo_mk0_v2C | Build Servo Mk0 V2 biped (shield, gun, digitigrade legs, idle/walk/attack). |
| create_summit_kold_deposit_v1C | Build Kold deposit V1 — low gold motes scattered on the ground. |
| create_summit_gentes_cyborg_v1C | Build Gentes Cyborg V1 — heavy infantry with minigun (idle/walk/attack). |
| create_summit_gather_drone_v1C | Build Robot Gather Drone V1 — square hover harvester with suction (idle/harvest). |
| create_summit_scavenger_v1C | Build Gentes Scavenger V1 — pickup harvester with front loader bucket (idle/harvest). |
| create_summit_zenox_ze_v1C | Build Zenox Ze V1 — sperm-like harvester with many tails (idle/walk/harvest). |
| create_summit_operations_center_v1C | Build Human Operations Center V1 — NORAD-style HQ with roof whirlybirds (idle). |
| create_summit_jaguar_afv_v1B | Build Human Jaguar AFV V1 — tracked turret tank with cannon + coax trace pivots (idle/walk). |
| validate_rts_assetC | Validate Summit RTS asset conventions (materials, tris, pivot, animations). |
| validate_rts_silhouetteB | RTS silhouette checks: forward axis, cab/wheels/arms/bucket, animated pivots. |
| render_rts_silhouette_previewB | Orthographic top-down PNG for RTS silhouette review (~35m camera). |
| render_previewC | Render a still preview PNG from the active camera. |
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 32 tools
Each tool has a highly specific and unique purpose, from creating individual RTS models (e.g., create_summit_bobcat) to distinct validation and export operations. No two tools appear to overlap in functionality, ensuring an agent can reliably select the correct tool.
Tool names follow a consistent verb_noun_snake_case pattern, with clear prefixes like create_, list_, validate_, and export_. Within each category, naming is uniform (e.g., create_summit_*_v# or validate_*), making the tool set predictable and easy to navigate.
32 tools is on the high side, but the server is focused on a specialized RTS asset pipeline, which justifies many specific model creators and validators. However, the sheer number may overwhelm agents, and some generic operations could be consolidated.
The tool set covers the full lifecycle for the Summit RTS asset domain: creation of multiple specific models, validation of conventions, animation management, and export. Minor gaps exist (e.g., no geometry or material editing), but core workflows are well supported.