BlenderMCP
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_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:
|
| 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. |
| 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 13 tools
Each tool has a clearly distinct purpose: downloading assets, generating models via images or text, checking statuses, getting scene/object info, searching, and applying textures. Even overlapping functions like generate_hyper3d_model_via_images and via_text are differentiated by input type.
Most tools follow a verb_noun pattern (e.g., download_polyhaven_asset, execute_blender_code), but there are minor deviations like 'poll_rodin_job_status' vs 'get_hyper3d_status' and mixed use of 'get_', 'search_', 'generate_'. The pattern is still recognizable and readable.
With 13 tools, the server covers Polyhaven integration (download, search, categories, status, set texture), Hyper3D generation (images/text, status, poll, import), and basic scene introspection. This is well-scoped for a Blender MCP server without being excessive or anemic.
The tool surface covers the core workflows for external asset integration (Polyhaven, Hyper3D) and provides code execution for flexibility. Minor gaps exist, such as no dedicated tool for deleting assets or listing objects, but these can be addressed via execute_blender_code.