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 Universal & Token

      domainjon
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to inspect and drive Blender scenes directly, either through a live editor bridge on port 8190 or automatically via headless background CLI when Blender is closed. Provides token-efficient tools for scene outlining, object creation and modification, modifiers, materials, rendering, asset export, and arbitrary bpy script execution.
      -

    • blender-mcp

      thanhdoancong127
      A
      license
      A
      quality
      B
      maintenance
      Lets agents see and drive a live 3D application session through its addon socket: viewport screenshots, turntable and multi-mode renders, scene and object inspection, arbitrary Python execution, GLB import/export and asset validation, plus rig, pose-deformation and silhouette-likeness checks. This lets an agent visually judge a 3D result instead of guessing.
      25
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 113 tools

    Disambiguation3/5

    The set spans many domains and contains numerous closely related tools, such as attach/move_to_contact/place_on/ground, subdivide/subdivide_faces/remesh, render_sheet/render_view/render_final, and set_material/procedural_material/assign_material_faces. The descriptions are unusually detailed and often explicitly compare alternatives, which helps a lot, but with 113 tools an agent still faces many near-overlapping choices.

    Naming Consistency4/5

    Almost all tool names use lower snake_case and are readable as verb_noun or noun forms, e.g. create_primitive, check_mesh, export_glb, list_materials. There are some bare nouns/verbs such as array, lathe, ground, pose, terrain, rock, and mixed patterns like check_* versus render_*, but the deviations are minor.

    Tool Count1/5

    113 tools is an extreme over-scoping for a single MCP server, far beyond the typical 3-15 well-scoped range. Even for a broad Blender automation server, many specialized operations could be consolidated or grouped, making the surface overwhelming.

    Completeness4/5

    For a broad Blender asset/level creation, materials, rendering, reference matching, rigging, and export server, the surface is very extensive and covers most core workflows. Missing areas such as animation keyframing, constraints/IK, advanced UV editing, and physics/simulation prevent a perfect score, but agents can accomplish a wide range of tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources