Skip to main content
Glama

Related Servers

Alternatives to ellmos Blender Use MCP

No user-submitted related servers found.

    Related Servers

    • 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
      C
      quality
      C
      maintenance
      Enables MCP-capable assistants to inspect, create, measure, and review Blender production workflows for characters, rigs, animation, game meshes, facial performance, secondary motion, and PBR materials with checkpoints and visual QA.
      274
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents and Blender users to generate game-ready art through a set of Blender tools covering concept image generation, image-to-3D mesh creation, mesh cleanup, PBR material assignment, greybox level layout, camera pathing and still or sequence rendering. Every action runs headless Blender, returns machine-readable JSON with pass/fail self-checks such as triangle budget, scale, pivot and clearance, so agents can verify and fix each step unattended.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables local creation and verification of Rhino .3dm architectural models from JSON specs without Rhino or a license, including inspection, two-view PNG rendering, evidence auditing, and optional Blender rendering/import.
      4
      Apache 2.0
    • F
      license
      A
      quality
      D
      maintenance
      A headless-first Model Context Protocol server for safe, deterministic Blender automation, exposing typed tools to inspect scenes and render previews without arbitrary command execution.
      3
      -

    TDQS

    B3.3/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool has a distinct purpose: locating the executable, running a script, and verifying FBX re-import. The only slight overlap is that verify_fbx_reimport is a specialized form of run_script, but the descriptions clarify their intended uses.

    Naming Consistency5/5

    All tool names follow a consistent 'blender_<verb>...' pattern (locate, run_script, verify_fbx_reimport). The naming convention is uniform and predictable.

    Tool Count5/5

    With only 3 tools, the set is tightly scoped to Blender automation workflows. Each tool serves a clear and necessary function, and the count is well within the expected range for a focused utility server.

    Completeness3/5

    The toolset covers the core workflow of locating Blender, running scripts, and verifying FBX files, but lacks generic ways to retrieve script output or handle other common Blender operations. This leaves some gaps for broader automation scenarios.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues