Skip to main content
Glama
YellowFoxH4XOR

Blender MCP

by YellowFoxH4XOR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Blender MCP

No user-submitted related servers found.

    Related Servers

    • Blender MCP Server

      cwahlfeldt
      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
      -

    • blendermcp

      ZNaiGaomu
      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

    • Maya MCP

      GimbalGoats
      A
      license
      B
      quality
      A
      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
      153 PyPI
      23
      MIT

    • Blender MCP Server

      BlkDem
      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

    • bMCP

      niewinny
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI to control Blender 3D through the Model Context Protocol, allowing Python execution, scene state queries, and automation of 3D workflows.
      5
      GPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityStale
    ResponsivenessNo issues

    Resources