Skip to main content
Glama

Related Servers

Alternatives to Stereograph

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects MCP-compatible clients to a live Blender scene for AI-assisted 3D workflows, enabling inspection and controlled operations on objects, materials, cameras, lights, render settings, animation, UVs, Geometry Nodes, imports, exports, and Python execution.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Connects MCP clients to a local Blender + Bonsai (BlenderBIM) session for scene inspection, IFC project querying, viewport screenshots, and executing Python code in Blender.
      8
      15
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote control of Blender through MCP, allowing code execution, scene manipulation, rendering, and file transfer in a containerized environment.
      1
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to control a running Blender instance through the Model Context Protocol, allowing scene inspection, object creation and editing, rendering, and execution of Blender Python. It works locally via a WebSocket bridge between the MCP server and a Blender add-on.
      15
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible clients to control Blender for modeling, materials, animation, physics, rendering, scene inspection, documentation search, and asset/generation service integration. It exposes a stdio endpoint with many Blender operations for creating and editing 3D content.
      AGPL 3.0
    • A
      license
      C
      quality
      B
      maintenance
      Enables an external MCP client to inspect and model in Blender through a local bridge, with typed operations scheduled on Blender's main thread and approval/credential checks for scene changes.
      171
      MIT

    TDQS

    B3/5.0

    Scored across 42 tools

    Disambiguation3/5

    Most tools target distinct Blender inspection or correction workflows, but the many live-vs-_for_cli variants and parallel preview/apply/cancel families create near-duplicate boundaries. An agent must read descriptions carefully to avoid confusing summary tools such as linked libraries, datablocks, path info or usage guess, especially across live and headless modes.

    Naming Consistency4/5

    Names are overwhelmingly snake_case with predictable verb_object patterns, and the _for_cli suffix is applied systematically. Minor deviations exist, such as blender_health and a few very long descriptive names, but there is no chaotic mixing of conventions.

    Tool Count2/5

    At 42 tools, the surface is substantially above the 3-15 sweet spot and feels heavy. Much of the bloat comes from duplicated live/_for_cli pairs and parallel preview/apply/cancel triples, though the broad Blender automation scope partly justifies some of the breadth.

    Completeness4/5

    The set covers file summaries, object and scene inspection, documentation search, screenshots, navigation, rendering, rig/motion/cloth review and corrective-edit workflows. Minor gaps remain, such as explicit save/undo or general object-editing tools, but execute_blender_code can bridge many of them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues