Skip to main content
Glama
a-homelab

Blender MCP

by a-homelab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Blender MCP

No user-submitted related servers found.

    Related Servers

    • Blender MCP Bridge

      oddyseex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to drive a live Blender session over MCP by creating and transforming primitives, building and assigning materials, inspecting scenes and objects, capturing viewport screenshots, and executing arbitrary bpy Python. Commands are relayed over a local TCP bridge to a Blender add-on and executed on Blender's main thread, supporting multiple simultaneous AI clients.
      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

    • blendy-blender-mcp

      chlxyz
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control and query Blender scenes through local MCP, allowing operations like retrieving scene information with objects and materials.
      -
    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.5/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools target clearly distinct actions or resources, and the _for_cli suffix cleanly separates live vs. background modes. However, the get_blendfile_summary_* family and the get_objects_summary/get_object_detail_summary pair are similar enough that an agent must read descriptions carefully to avoid misselection.

    Naming Consistency4/5

    Tool names are uniformly snake_case and verb-first (get_, jump_to_, render_, execute_, search_), which is predictable and readable. Minor inconsistencies like get_screenshot_of_window_as_json returning layout JSON rather than an image, and mixed get_blendfile_summary_of_* vs. get_blendfile_summary_* patterns, keep it from a perfect score.

    Tool Count2/5

    At 26 tools, the server exceeds the 25-tool threshold for 'too many,' and the six nearly identical _for_cli variants inflate the count without adding much conceptual breadth. The core categories are sensible, but merging live/CLI variants into single parameterized tools would make the surface much cleaner.

    Completeness4/5

    The set covers scene inspection, object details, screenshots, navigation, rendering, documentation search, and blend-file health checks, which is broad coverage for Blender. There are no dedicated mutation tools beyond execute_blender_code, but that escape hatch plus the CLI variants covers most workflows, leaving only minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources