blender-studio-pro-mcp
Related Servers
Alternatives to blender-studio-pro-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Blender that connects to the official Blender Lab add-on, exposing 27 tools for scene manipulation, object editing, materials, rendering, and Python execution through the add-on's actual wire protocol.27MIT
- AlicenseCqualityBmaintenanceMCP server providing 138+ tools to control Blender 4.2 LTS, enabling modeling, coloring, rigging, animation, geometry nodes, UV, printing, batch operations, and IO through natural language from any AI assistant.1001MIT
- AlicenseCqualityCmaintenanceComprehensive MCP server for Blender with 308 tools across 25 modules, enabling AI-powered 3D creation and full VRChat avatar pipeline.1004MIT
- AlicenseCqualityDmaintenanceMCP server that enables AI to control Blender 3D, providing 175 typed tools for objects, materials, animation, compositing, and more via the Model Context Protocol.1002MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI agents to control Blender through natural language for 3D scene creation, animation, and rendering. It provides over 550 actions and direct Python execution via a bridge to a live local Blender session.6MIT
- AlicenseNot gradedqualityCmaintenanceTransforms Blender into an MCP server with 50+ tools for AI-driven 3D workflows, enabling complete control over objects, materials, animations, physics simulations, and rendering through natural language commands.45MIT
TDQS
Scored across 223 tools
Several tools overlap significantly: call_operator and execute_python can perform the work of many dedicated commands, create_object overlaps with create_camera/create_light/create_curve, and frame_selected vs frame_selected_objects are nearly identical names for different operations. With 223 tools, an agent will frequently struggle to select the correct one.
The overwhelming majority of tools follow a clear lower_snake_case verb_noun pattern, with create/add/set/list used fairly consistently. Minor inconsistencies like gn vs geometry_nodes, gp vs grease_pencil, and a few standalone verbs like undo/redo prevent a perfect score.
At 223 tools, this is far beyond the heavy threshold and includes both a complete bpy.ops bridge and extensive dedicated high-level commands, creating massive redundancy. This extreme count makes the server unnecessarily difficult to navigate.
The server covers nearly every Blender domain--modeling, materials, animation, physics, rendering, geometry nodes, sequencer, and more--while also exposing call_operator, execute_python, and set_attr_path as universal escape hatches. There are no obvious dead ends in the tool surface.