Skip to main content
Glama

Related Servers

Alternatives to bl-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to drive a live Blender session for modeling, shading, lighting, rendering, and scene manipulation, returning rendered images for visual feedback.
      4
      122
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables 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.
      74
      GPL 3.0
    • F
      license
      A
      quality
      B
      maintenance
      Enables 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.
      3
      1
      -
    • A
      license
      C
      quality
      B
      maintenance
      Enables 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.
      209
      2
      MIT

    TDQS

    A3.6/5.0

    Scored across 113 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues