BlenderMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLENDER_HOST | No | Host address for Blender socket server | localhost |
| BLENDER_PORT | No | Port number for Blender socket server | 9876 |
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_scene_infoB | Get detailed information about the current Blender scene |
| get_object_infoB | Get detailed information about a specific object in the Blender scene. Parameters:
|
| get_viewport_screenshotA | Capture a screenshot of the current Blender 3D viewport. Parameters:
Returns the screenshot as an Image. |
| execute_blender_codeB | Execute arbitrary Python code in Blender. Make sure to do it step-by-step by breaking it into smaller chunks. Parameters:
|
| get_polyhaven_categoriesA | Get a list of categories for a specific asset type on Polyhaven. Parameters:
|
| search_polyhaven_assetsA | Search for assets on Polyhaven with optional filtering. Parameters:
Returns a list of matching assets with basic information. |
| download_polyhaven_assetA | Download and import a Polyhaven asset into Blender. Parameters:
Returns a message indicating success or failure. |
| set_textureA | Apply a previously downloaded Polyhaven texture to an object. Parameters:
Returns a message indicating success or failure. |
| get_polyhaven_statusA | Check if PolyHaven integration is enabled in Blender. Returns a message indicating whether PolyHaven features are available. |
| get_hyper3d_statusA | Check if Hyper3D Rodin integration is enabled in Blender. Returns a message indicating whether Hyper3D Rodin features are available. Don't emphasize the key type in the returned message, but sliently remember it. |
| get_sketchfab_statusA | Check if Sketchfab integration is enabled in Blender. Returns a message indicating whether Sketchfab features are available. |
| search_sketchfab_modelsA | Search for models on Sketchfab with optional filtering. Parameters:
Returns a formatted list of matching models. |
| download_sketchfab_modelA | Download and import a Sketchfab model by its UID. Parameters:
Returns a message indicating success or failure. The model must be downloadable and you must have proper access rights. |
| generate_hyper3d_model_via_textA | Generate 3D asset using Hyper3D by giving description of the desired asset, and import the asset into Blender. The 3D asset has built-in materials. The generated model has a normalized size, so re-scaling after generation can be useful. Parameters:
Returns a message indicating success or failure. |
| generate_hyper3d_model_via_imagesA | Generate 3D asset using Hyper3D by giving images of the wanted asset, and import the generated asset into Blender. The 3D asset has built-in materials. The generated model has a normalized size, so re-scaling after generation can be useful. Parameters:
Only one of {input_image_paths, input_image_urls} should be given at a time, depending on the Hyper3D Rodin's current mode. Returns a message indicating success or failure. |
| poll_rodin_job_statusA | Check if the Hyper3D Rodin generation task is completed. For Hyper3D Rodin mode MAIN_SITE: Parameters: - subscription_key: The subscription_key given in the generate model step. For Hyper3D Rodin mode FAL_AI: Parameters: - request_id: The request_id given in the generate model step. |
| import_generated_assetA | Import the asset generated by Hyper3D Rodin after the generation task is completed. Parameters:
Only give one of {task_uuid, request_id} based on the Hyper3D Rodin Mode! Return if the asset has been imported successfully. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| asset_creation_strategy | Defines the preferred strategy for creating assets in Blender |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Most tools have distinct purposes, but there is some overlap and ambiguity. For example, download_polyhaven_asset and set_texture both handle Polyhaven assets, but one downloads and imports while the other applies textures, which could confuse agents about workflow steps. Similarly, generate_hyper3d_model_via_images and generate_hyper3d_model_via_text are clearly different in input method, but their similar names and shared import functionality might lead to misselection if the agent isn't careful. Overall, descriptions help clarify, but the boundaries aren't perfectly clear.
Tool names follow a consistent verb_noun pattern with snake_case throughout, such as download_polyhaven_asset, get_scene_info, and search_sketchfab_models. There are minor deviations like execute_blender_code (which uses 'execute' instead of 'run' or similar, but it's still a verb) and poll_rodin_job_status (which includes 'job' in the noun part, slightly breaking the pure verb_noun flow). Overall, the naming is highly predictable and readable.
With 17 tools, the count is slightly high but reasonable for a Blender integration server that covers multiple external services (Polyhaven, Sketchfab, Hyper3D) and core Blender operations. It feels comprehensive rather than bloated, as each tool serves a specific function like downloading assets, generating models, or getting scene info. However, it borders on being heavy, which might overwhelm agents but is justified by the broad scope.
The tool set provides good coverage for asset sourcing (Polyhaven, Sketchfab), 3D model generation (Hyper3D), and scene management in Blender. It includes key operations like download, search, status checks, and import. Minor gaps exist, such as no tools for editing or deleting objects in Blender beyond basic info retrieval, and limited texture management (only set_texture without broader material handling). Agents can work around these, but the surface isn't fully comprehensive for advanced Blender workflows.