No user-submitted related servers found.
Scored across 148 tools
Many tools have overlapping purposes, e.g., solidify_mesh, add_wall_thickness, and add_modifier with SOLIDIFY; get_scene_info, get_scene_graph, and get_objects_summary all provide scene summaries. The distinction between create_object, model_from_scratch, and rig_from_scratch is also unclear, making it hard for an agent to pick the right operation.
Most tools follow a verb_noun pattern (create_object, list_materials, set_render_engine), but there are notable deviations like 'ping', 'measure', 'find_objects', 'array_object', and 'run_batch'. The mix of generic verbs (get, set, create, add, remove) is consistent, but compound phrases like 'setup_three_point_lighting' and 'colorize_from_scratch' break the pattern.
With 148 tools plus a registry of 228, the server is extremely over-scoped. This is far beyond the typical 3-15 tool range and even exceeds the 50+ threshold, making selection overwhelming and redundant. The count is clearly inappropriate for a coherent MCP server.
The tool surface covers a vast range of Blender operations: modeling, materials, lighting, animation, rigging, UV, geometry nodes, import/export, and scripting. The registry tools and run_batch provide a fallback for any missing operation. Minor gaps exist, such as no direct tool to delete a material or edit text content, but these are workaround-able via execute_blender_code or call_registry_tool.