blender-mcp
Related Servers
Alternatives to blender-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceConnects Blender to Claude AI through the Model Context Protocol, enabling prompt-assisted 3D modeling, scene creation, and manipulation.22MIT
- AlicenseAqualityDmaintenanceConnects Blender to Claude AI via the Model Context Protocol, enabling natural language-driven 3D modeling, scene creation, and manipulation.22MIT
- AlicenseBqualityDmaintenanceConnects Blender to Claude AI through the Model Context Protocol, enabling AI-assisted 3D modeling, scene creation, and manipulation through natural language commands.172MIT
- AlicenseAqualityDmaintenanceConnects Blender to Claude AI through the Model Context Protocol, enabling natural language control of 3D modeling, scene creation, and manipulation.22MIT
- AlicenseBqualityDmaintenanceConnects Blender to Claude AI through the Model Context Protocol (MCP), enabling prompt-assisted 3D modeling, scene creation, and manipulation.17MIT
- AlicenseBqualityDmaintenanceConnects Blender to Claude AI through the Model Context Protocol (MCP), enabling prompt-assisted 3D modeling, scene creation, and manipulation directly from Claude.17MIT
TDQS
Scored across 22 tools
Tools are mostly distinct by service (Polyhaven, Sketchfab, Hyper3D, Hunyuan3D), but there is overlap between generate_hyper3d_model_via_text/images and generate_hunyuan3d_model (which also accepts images). import_generated_asset is ambiguous because it doesn't specify the service, unlike import_generated_asset_hunyuan.
Naming is predominantly verb_noun with snake_case, but there are inconsistencies: poll_rodin_job_status uses 'rodin' instead of 'hyper3d', import_generated_asset lacks a service qualifier, and set_texture is vague. The pattern is mostly readable but not uniformly applied.
22 tools is on the higher end but appropriate given the server integrates four asset services (Polyhaven, Sketchfab, Hyper3D, Hunyuan3D) plus core scene inspection and code execution. Each integration requires status, search/download, generation, and polling tools, so the count is justified.
The tool surface covers the full asset pipeline lifecycle: search, preview, download, generate, poll, import, and status checks for each integration, plus scene/object info. Missing direct object manipulation tools (e.g., update/delete) are compensated by execute_blender_code, but dedicated tools would be more complete.