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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_scene_infoB | Get detailed information about the current Blender scene |
| get_object_infoC | |
| get_viewport_screenshotA | |
| execute_blender_codeB | |
| get_polyhaven_categoriesA | |
| search_polyhaven_assetsA | |
| download_polyhaven_assetA | |
| set_textureA | |
| 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_statusB | Check if Sketchfab integration is enabled in Blender. Returns a message indicating whether Sketchfab features are available. |
| search_sketchfab_modelsA | |
| download_sketchfab_modelC | |
| generate_hyper3d_model_via_textA | |
| generate_hyper3d_model_via_imagesA | |
| poll_rodin_job_statusA | |
| import_generated_assetA | |
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, such as downloading assets from different sources (Polyhaven, Sketchfab), generating models via Hyper3D, and getting scene/object info. However, there is some overlap between 'generate_hyper3d_model_via_images' and 'generate_hyper3d_model_via_text' as both generate Hyper3D assets, which could cause confusion if the user is unsure which input method to use, though their descriptions clarify the difference.
All tool names follow a consistent snake_case pattern with clear verb_noun structures, such as 'download_polyhaven_asset', 'execute_blender_code', and 'get_scene_info'. There are no deviations in naming conventions, making the set predictable and easy to parse for an agent.
With 17 tools, the count is slightly high but reasonable for a Blender integration server that covers asset downloading, model generation, scene management, and status checks. It feels comprehensive without being overwhelming, though it borders on the upper limit of typical scoping (3-15 tools).
The tool surface covers key areas like asset import (Polyhaven, Sketchfab, Hyper3D), scene inspection, and basic operations (e.g., screenshot, code execution). Minor gaps exist, such as no tools for editing or deleting objects in Blender, but agents can work around this using 'execute_blender_code' for custom operations, ensuring core workflows are supported.