No user-submitted related servers found.
Scored across 307 tools
The tool set is riddled with overlapping and duplicate operations: add_modifier vs modifier_add, set_keyframe vs anim_insert_keyframe, create_armature vs armature_create, material_list vs list_materials, smart_uv_project vs uv_smart_unwrap, add_rigid_body vs physics_add_rigid_body, render_image vs render_still, export_scene vs io_export_*, and many more. An agent would constantly struggle to know which of several near-identical tools to call.
Naming is chaotic: verb-first names like create_object and delete_object sit alongside domain-first names like modifier_add and anim_insert_keyframe, and the same action appears in both styles (add_modifier/modifier_add, create_collection/scene_create_collection, create_armature/armature_create). Prefixes are applied arbitrarily across dozens of domains, with no consistent pattern.
With 307 tools, this is an extreme mismatch for an MCP server's typical scope. The count is 5-10x even what a very heavy integration should expose, and the massive redundancy makes the size worse rather than more useful. It overwhelms agents and violates the principle that each tool should earn its place.
Coverage across the Blender and VRChat avatar workflow is remarkably broad: modeling, sculpting, materials, modifiers, animation, physics, UV, geometry nodes, rigging, Unity integration, rendering, and import/export are all represented. Minor gaps exist, such as no direct material deletion, no delete_collection, and no bone removal tool, but these are workarounds via execute_code or scene_cleanup.