blend-ai
Related Servers
Alternatives to blend-ai
No user-submitted related servers found.
Related Servers
- 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
- 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.7MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables AI models to directly control Blender for 3D modeling, scene manipulation, and material management through natural language. It supports advanced workflows including Python code execution, viewport visualization, and integration with external asset libraries like Poly Haven and Hyper3D.221MIT
- 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 gradedqualityDmaintenanceAn MCP server that enables AI assistants like Codex or ChatGPT to inspect and control a local Blender scene, including creating objects, editing materials, setting cameras and lights, rendering previews, and saving safe copies of .blend files.MIT
- 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 186 tools
With 186 tools, several areas overlap: multiple boolean tools (booltool_auto_*, boolean_operation, add_modifier with BOOLEAN), multiple material creation paths (create_material, create_principled_material), and generic vs specific setters (set_material_property vs set_shader_node_input). Descriptions often clarify, but the sheer volume creates potential for misselection.
Tool names consistently use snake_case verb_noun (or verb_preposition_noun) patterns throughout, with no mixing of camelCase or other conventions. Prefixes like booltool_auto_ are used consistently within their group.
186 tools far exceeds the suggested 3-15 range and is an extreme mismatch even for a complex domain like Blender. Many tools could be consolidated (e.g., separate setters for location/rotation/scale).
The tool set covers a vast surface: object/mesh/materials, shaders, rendering, animation, physics, geometry nodes, and file I/O. However, notable lifecycle gaps exist for constraints (only add, no edit/remove/list) and armature bones (add only, no remove/edit), though execute_blender_code provides a workaround.