Skip to main content
Glama

Related Servers

Alternatives to ellmos Blender Use MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      3
      Apache 2.0
    • F
      license
      A
      quality
      C
      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
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and MCP clients to perform 3D asset creation and verification: exact b-rep CAD, GLB validation with embedded certificates, mesh inspection, and physics scenes, with most tools running without Blender.
      36
      81 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables safe, repeatable preparation of game characters in Blender through high-level MCP tools for validation, import, normalization, action renaming, and GLB export, with dry-run by default and loopback-only security.
      9
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables safe, structured control of Blender on Windows via a standalone STDIO MCP server, providing seven tools to inspect scenes, list and edit materials, transform objects, add modifiers, set smooth shading, and export assets without arbitrary code execution.
      7
      Apache 2.0

    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

    ActivityActive
    ResponsivenessNo issues