Skip to main content
Glama

Related Servers

Alternatives to Blender MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows management and execution of Blender Python scripts, enabling users to create, edit and run scripts in a headless Blender environment through natural language interfaces.
      11
      -
    • 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
      B
      maintenance
      A local Model Context Protocol server for controlling Autodesk Maya, providing typed tools for scene, modeling, animation, and more without Maya imports in the server process.
      71
      240 PyPI
      27
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a live Blender session through Model Context Protocol tools for scene and object manipulation, rendering, PolyHaven asset handling, and runtime-switchable LLM backends. It supports local and OpenAI-compatible providers, allowing prompts and provider configuration changes without restarting the server.
      -
    • 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

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: checking environment status, inspecting a blend file, and rendering a preview. No two tools overlap in function.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_blender_status, inspect_scene, render_preview), making the intended action obvious.

    Tool Count4/5

    Three tools is at the low end of the typical well-scoped range, but each serves a distinct function without redundancy. The count feels minimal rather than excessive.

    Completeness2/5

    The server lacks any tools for creating, editing, or saving Blender scenes, which are common operations for a Blender integration. The existing tools only cover a narrow inspect-and-render workflow, leaving significant gaps for general-purpose use.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues