Skip to main content
Glama
asedias

bl-mcp

by asedias
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to bl-mcp

No user-submitted related servers found.

    Related Servers

    • blender-mcp

      Mishaadevv
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to drive a live Blender session for modeling, shading, lighting, rendering, and scene manipulation, returning rendered images for visual feedback.
      122
      MIT

    • Blender Open MCP

      TeresaZawadzki98
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a live Blender session, inspect and modify scenes, manage PolyHaven assets, render images, and route prompts through configurable local or OpenAI-compatible LLM backends.
      -

    • Blender Open MCP

      joaoa81427
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a live Blender session, creating, modifying, and deleting objects, applying materials, rendering images, executing code, and pulling PolyHaven assets, while routing prompts through a provider-agnostic LLM backend that can be switched at runtime.
      -

    • Blender Agent

      patrickleehua
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts and coding agents to model, inspect, measure, and deliver real Blender scenes through 15 tools and 217 catalog operations, returning actual rendered images after key edits. Works against a live Blender GUI via addon or a persistent headless worker, producing editable .blend files, GLB exports, previews, and acceptance records.
      1
      BSD 3-Clause
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources