Grok2Blender
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_blender_statusC | Get Blender addon connection status. |
| get_scene_summaryC | Get compact scene graph. |
| get_object_detailsC | Get object transform and materials. |
| take_viewport_screenshotD | Capture viewport PNG for vision. |
| set_safe_modeD | Toggle safe mode. |
| set_dry_runD | Toggle dry-run mode. |
| undo_last_operationC | Undo last Grok2Blender operation. |
| autosave_blendC | Create timestamped blend backup. |
| confirm_destructive_actionC | Acknowledge a destructive operation for safe-mode gating. |
| create_project_structureC | Initialize project folders. |
| import_assetC | Import glTF/FBX/USD/OBJ. |
| create_primitiveD | Create mesh primitive. |
| transform_objectsD | Transform named objects. |
| organize_hierarchyC | Parent objects and move to collections. |
| delete_objectsC | Delete objects (confirm in safe mode). |
| apply_material_presetD | Apply material preset. |
| setup_lookdev_stageC | Create lookdev turntable stage. |
| assign_materialC | Assign material preset to object. |
| setup_hdri_environmentC | Configure HDRI world shader. |
| create_three_point_lightingC | Create three-point lighting rig. |
| create_area_light_rigC | Create area light rig. |
| create_cameraC | Create cinematic camera. |
| set_active_cameraC | Set active render camera. |
| frame_camera_on_objectC | Frame camera on object. |
| export_camera_dataC | Export camera JSON. |
| insert_keyframeD | Insert object keyframe. |
| animate_camera_push_inC | Animate camera push-in. |
| set_timeline_rangeD | Set timeline range. |
| configure_render_settingsD | Configure render engine. |
| render_previewC | Render preview still. |
| render_animation_sequenceC | Render animation sequence. |
| export_alembic_cacheD | Export Alembic cache. |
| export_usd_stageD | Export USD stage. |
| export_render_passesD | Export render passes. |
| create_shot_metadataC | Create shot metadata JSON. |
| prepare_grs_handoffC | Emit GRS payload for Resolve import. |
| suggest_fusion_setupC | Suggest Fusion node setup for Blender previz import. |
| generate_blender_scriptC | Generate standalone bpy 4.2+ script for offline execution. |
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 38 tools
Most tools have distinct purposes, but 'apply_material_preset' and 'assign_material' overlap significantly in description, potentially confusing an agent. Otherwise, tools are clearly separated.
All tool names follow a consistent verb_noun pattern in snake_case, with no mixed conventions or irregularities. Examples include 'create_camera', 'export_alembic_cache', and 'set_dry_run'.
With 38 tools, the count is high for a typical MCP server, but each tool addresses a specific operation in a broad domain (Blender 3D). It borders on excessive but is still manageable.
The tools cover creation, lighting, animation, rendering, and export, but lack editing operations (e.g., mesh modifiers, materials editing) and advanced features like physics or rigging. Gaps exist for a general Blender workflow.