bl-mcp
Related Servers
Alternatives to bl-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI agents to drive a live Blender session for modeling, shading, lighting, rendering, and scene manipulation, returning rendered images for visual feedback.4122MIT
- AlicenseCqualityBmaintenanceEnables AI assistants to drive a live Blender session through 74 structured, allowlisted tools covering scene management, mesh modeling, modifiers, materials, lighting, rigging, animation, physics, rendering, and multi-step orchestration — all without eval/exec and with localhost-only, token-authenticated, thread-safe bridging. Supports planning and visual validation of preview renders for end-to-end 3D workflows.74GPL 3.0
- AlicenseAqualityBmaintenanceEnables AI agents to drive Blender 5.1+ for modeling, sculpting, mesh editing, scene management, and rendering through live Python execution.261MIT
- FlicenseAqualityBmaintenanceEnables an AI assistant to operate a running Blender instance through 428 typed, parameter-checking tools for modeling, materials, UVs, rigging, animation, physics, geometry nodes, and rendering, while reading results back.31-
- AlicenseCqualityBmaintenanceEnables AI agents to control Blender through 150+ tools across 24 modules, including modeling, materials, lighting, animation, rendering, mesh quality analysis, and visual feedback, plus expert prompts and goal-first workflow management.2092MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create and manipulate 3D scenes, objects, and materials, execute Blender Python, capture visual verification views, and generate or import assets and models.MIT
TDQS
Scored across 113 tools
Despite 113 tools, descriptions actively disambiguate overlapping operations by explicitly cross-referencing alternatives (subdivide vs subdivide_faces vs remesh; attach vs move_to_contact vs place_on vs ground; combine vs array vs mirror vs duplicate). The many face-editing tools (extrude_faces, inset_faces, delete_faces, sculpt, transform_region, etc.) share one `where` selector and similar framing, which creates some residual cognitive load, but each targets a distinct operation.
Names are thoroughly snake_case with predictable verb_noun or noun patterns (create_primitive, add_light, check_mesh, set_material, delete_faces). Minor deviations exist: many tools are noun-only (limb, blob, rock, terrain, loft, sweep, boolean) and some compound oddities (palette_uv, noise_displace), but casing and style stay consistent throughout.
113 tools is far beyond what any single agent can hold in working context, even for a domain as broad as full 3D modeling, and exceeds the rubric's 50+ 'extreme mismatch' band. The breadth of Blender (modeling, materials, rendering, rigging, level design, reference matching) partly justifies the volume, but the surface is heavy and hard to navigate as a set.
The surface covers an extraordinary lifecycle: primitives and mesh editing, transforms, materials/UV/baking, rendering and post, rigging and posing, export/import with checks, plus verification tools (assert_spec, check_game_ready, compare_view, diff_since) and safety nets (checkpoint, rollback, job_status). Almost no domain gap is left uncovered for a Blender automation agent.