Skip to main content
Glama
Berrio
by Berrio

Related Servers

Alternatives to blender-MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables secure, local automation of Blender through typed MCP tools for scene, modeling, material, animation, rendering, and file workflows via an authenticated loopback bridge.
      173
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables AI clients to control background Blender jobs over stdio so they can inspect a 3D character or companion model, calibrate its anatomy and named bones, bake and export animation, and numerically verify the persisted GLB for playback review. Includes a CLI, models and workspaces that stay local unless explicitly shared.
      9
      MIT
    • 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 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
    • 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
      -

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct stage or aspect of the character pipeline: status, scene info, object listing, import, creation, validation, normalization, action renaming, and export. There is no meaningful overlap between tool purposes, and descriptions clearly distinguish read-only actions from mutating ones.

    Naming Consistency4/5

    All tools share the 'blender_' prefix and use snake_case, with most following a verb_noun pattern (import_asset, list_objects, validate_character). The exceptions are blender_status and blender_scene_summary, which use noun-only or noun_noun naming, creating a minor inconsistency.

    Tool Count5/5

    With 9 tools, the set is well-scoped for the stated domain of Blender character preparation and export. Each tool covers a necessary step without redundant or excessive additions, fitting comfortably within the ideal 3-15 range.

    Completeness4/5

    The toolset covers the core lifecycle for character assets: import, create, validate, normalize, rename actions, and export. Minor gaps exist (e.g., no tool for direct editing of meshes or armatures), but the provided suite is sufficient for a complete character pipeline from import to game-ready export.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues