Skip to main content
Glama
full-aigc-plugins

partme_blender

by full-aigc-plugins
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to partme_blender

No user-submitted related servers found.

    Related Servers

    • MCP Blender

      joel1251
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM clients like Claude to control Blender remotely, including scene inspection, object creation/modification, and Python code execution, via a socket-based MCP server.
      321 npm
      MIT

    • Blender MCP

      tattooinmtl
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP client to drive Blender 5.2 LTS through natural language, with tools for scene inspection, object creation and transformation, material and modifier handling, rendering, viewport capture, and guarded Python execution.
      2
      MIT

    • blender-research-mcp

      Haiyang-Bian
      F
      license
      B
      quality
      B
      maintenance
      Enables safe, observable Blender research by exposing structured tools for viewport capture, object and material edits, semantic scene creation, and managed .blend project lifecycles with transactional rollback and validation.
      42
      -

    • blender-server-mcp-docker

      BATTLEHAWK00
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote control of Blender through MCP, allowing code execution, scene manipulation, rendering, and file transfer in a containerized environment.
      1
      -
    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

    C2/5.0

    Scored across 173 tools

    Disambiguation3/5

    Most tools are clearly separated by domain prefix and action, but the sheer number creates several near-overlaps: object.create_curve vs curve.create, material.attach_image_texture vs material.connect_image_texture, and capability.list vs session.capabilities. The boilerplate descriptions provide no semantic detail, so agents must rely on command names alone to disambiguate.

    Naming Consistency5/5

    Every tool follows the consistent blender_<domain>_<action> pattern in snake_case, e.g. blender_object_duplicate, blender_modifier_remove, blender_uv_pack. Even multi-word domains like geometry_nodes and grease_pencil use the same convention, making the naming highly predictable.

    Tool Count1/5

    With 173 tools, this far exceeds the 50+ threshold for an extreme mismatch. While Blender is a large application, exposing nearly the entire harness surface as individual tools creates an overwhelming selection space and model-context burden.

    Completeness4/5

    The tool surface covers a very wide range of Blender domains: animation, rigging, sculpting, simulation, rendering, VFX tracking, UV, materials, geometry nodes, and validation. Minor gaps remain, such as no explicit save/open file management or a direct render trigger, but they are workable for most automation workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources