Skip to main content
Glama

Related Servers

Alternatives to Blender MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable AI clients to control a local Blender workstation through a secure HTTP gateway for 3D scene inspection, modeling, rigging, animation, materials, rendering, import/export, and controlled Python automation. Supports permission profiles and authentication modes to keep Blender execution local while allowing AI-assisted production workflows.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to interact with a local Blender desktop application through a TCP bridge for scene inspection, rendering, asset export, visual comparison, and controlled mesh operations.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to securely read and write local files, run whitelisted commands and Git operations, manage long-running jobs, and hand off work across sessions through a self-hosted bridge with OAuth, audit logging, and desktop controls.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI clients to discover, inspect, and run 2,000+ AI models and data APIs—including LLMs, image, video, and audio generation—through a single authenticated local bridge with per-call pricing shown before execution. It also supports run status tracking, account balance checks, and rollback from one browser sign-in.
      556,724 npm
      MIT

    TDQS

    C2.2/5.0

    Scored across 156 tools

    Disambiguation2/5

    Many tools overlap heavily: get_materials vs list_materials, get_modifiers vs list_modifiers, get_scene_info vs get_scene_summary, and create_primitive vs dozens of primitive-specific creators. Render/capture tools also blur together (render_scene, render_preview, render_final; capture_viewport, get_viewport_screenshot, capture_scene_preview). An agent can still pick a reasonable tool in many cases, but several boundaries are genuinely unclear.

    Naming Consistency3/5

    The surface is overwhelmingly snake_case, but verb conventions are inconsistent: get_ and list_ are used interchangeably for the same resource (materials/modifiers), some tools are noun-only (camera_view, mesh_cleanup, organize_scene), and capture_ vs render_ vs get_ overlap conceptually. It remains readable, but the naming does not reliably encode resource+action.

    Tool Count1/5

    156 tools is far beyond a well-scoped surface, even for a broad Blender domain. The set contains many convenience wrappers and near-duplicates (create_sphere, create_uv_sphere, create_primitive, create_cube, etc.) that inflate the count without adding distinct capability.

    Completeness5/5

    Coverage is extremely broad: scene/object inspection, mesh editing, materials and nodes, cameras, lights, rendering, animation, assets, file operations, collections, viewport capture, and Python execution. Almost every core Blender workflow appears represented, with no obvious lifecycle dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues