No user-submitted related servers found.
Scored across 218 tools
The set contains several near-duplicate tools that make agent selection hard: blender_refine_iteration and blender_ai_refine both describe the same render-evaluate-suggest loop, and blender_ai_list_backends overlaps heavily with blender_ai_probe_backends. Many workflows also have two parallel implementations (e.g., blender_scatter_on_surface vs blender_geonode_scatter_instances), so boundaries are often unclear even when individual descriptions are good.
Most tools follow a clear blender_<domain>_<action> or blender_<domain>_<noun> snake_case pattern, which makes large chunks like blender_object_*, blender_mesh_*, and blender_msfs_* predictable. Deviations exist (blender_undo, blender_save, blender_silhouette_compare, blender_mesh_proportional_transform, blender_sculpt_to_retopo), but they are few compared to the 218-tool surface.
218 tools is an extreme count for any MCP server, far beyond the threshold where a toolset becomes unwieldy. The surface tries to cover entire Blender plus MSFS and AI pipelines in one server, making discovery and selection expensive for agents.
The domain coverage is impressively broad: object/scene lifecycle, mesh editing, materials, animation, rendering, physics, rigging, sculpting, baking, geometry nodes, and MSFS-specific workflows are all present. Minor gaps exist (no material_delete, no constraint_remove, no individual object visibility toggle, no render samples/output settings), but agents can often work around them via blender_execute_script.