Skip to main content
Glama
MITHRAN-BALACHANDER

Blender MCP Bridge

by MITHRAN-BALACHANDER
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Blender MCP Bridge

No user-submitted related servers found.

    Related Servers

    • 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

    • Chat with Blender

      Akerdogmus
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to control Blender 3D modeling and rendering through natural language commands via the Model Context Protocol.
      MIT

    • blender-mcp

      zorak1103
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to control Blender for 3D scene creation, object manipulation, material assignment, shader configuration, modifier application, keyframing, and rendering via the Model Context Protocol.
      2
      GPL 3.0

    • Blender MCP Link

      ENG-cpu-bit
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interactive control of Blender for 3D scene manipulation, geometry creation, material application, and viewport rendering via natural language prompts through the Model Context Protocol.
      MIT

    • BlenderMCP

      omniconnexsynapse
      A
      license
      B
      quality
      C
      maintenance
      Connects Blender to AI through the Model Context Protocol to enable prompt-assisted 3D modeling and scene manipulation. It supports object creation, material control, and arbitrary Python code execution directly within the Blender environment.
      22
      MIT

    • mcp-opencode-blender

      khalidSAT
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables programmatic control of Blender via OpenCode, supporting 3D model creation, material application, and export through a Model Context Protocol server.
      MIT
    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.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: blender_exec runs Python scripts, get_blender_scene retrieves scene information, and image_to_3d_model creates 3D models from images. The descriptions reinforce these distinct functions, making misselection unlikely.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (blender_exec, get_blender_scene, image_to_3d_model) with clear actions and targets. The minor deviation is that 'blender_exec' uses an abbreviation while others are spelled out, but the pattern remains readable and predictable.

    Tool Count3/5

    With only 3 tools, the set feels thin for a Blender bridge, as it lacks core operations like modifying objects, rendering, or exporting. While the tools are well-defined, the count is borderline low for the apparent scope of 3D modeling and automation.

    Completeness2/5

    There are significant gaps in the tool surface for a Blender integration. Missing are essential CRUD operations (e.g., create/update/delete objects), rendering tools, export capabilities, and scene manipulation functions. This will likely cause agent failures when trying to perform common Blender workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources