blender-mcp
Related Servers
Alternatives to blender-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceBlenderMCP enables Claude AI to directly interact with and control Blender for prompt-assisted 3D modeling, scene creation, and manipulation. It supports object and material control, scene inspection, and execution of Python code through natural language commands.17MIT
- AlicenseAqualityDmaintenanceConnects Blender to Claude AI and Cursor via MCP, enabling 3D modeling and scene manipulation through natural language.1311MIT
- 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
- FlicenseNot gradedqualityDmaintenanceEnables natural language control of Blender 3D through local AI models, allowing MCP clients to create, modify, and render scenes, apply materials, and execute Python code in Blender.-
- AlicenseAqualityDmaintenanceConnects Blender to Claude AI through MCP, allowing Claude to directly interact with and control Blender for 3D modeling, scene creation, and manipulation.22MIT
TDQS
Scored across 71 tools
Many tools overlap heavily: standalone create_collection, list_scenes, clear_scene duplicate operations inside blender_scene; blender_addons and manage_blender_addons are aliases; construct_object and manage_object_construction both build objects from natural language. Agents will struggle to pick the right tool when the same capability is exposed through multiple entry points.
Naming mixes conventions: verb_noun (create_collection, list_scenes), noun_specific (blender_mesh, blender_scene), generic (config_get, server_info), and verbose portmanteaus (agentic_blender_workflow, intelligent_3d_processing). The blender_ prefix is used inconsistently, and there is no clear predictable pattern across the tool set.
71 tools is an extreme count, far exceeding even the 50+ threshold for a mismatch. While many tools consolidate operations via portmanteau patterns, the sheer number of exposed tools overwhelms context windows and makes selection impractical for an agent.
The set covers an exceptionally broad range of Blender workflows: modeling, animation, rigging, materials, rendering, VSE, sculpt, physics, import/export, AI generation, asset repositories, and platform validation. Despite some missing micro-features (e.g., explicit file save), the surface is remarkably complete for its stated purpose.