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.
      222 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.
      1
      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
      -

    • 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

    • 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.2/5.0

    Scored across 184 tools

    Disambiguation5/5

    Each tool is namespaced by domain (e.g., animation, rig, object) with a specific action, making purposes clear and distinct. Even within the same area, actions like add_node vs. create_group vs. set_input are well-separated.

    Naming Consistency5/5

    All tools follow the consistent pattern blender_<domain>_<subdomain>_<action> or blender_<domain>_<action>. The naming is uniform and predictable, with no mixed conventions or vague verbs.

    Tool Count1/5

    At 184 tools, this server vastly exceeds any practical tool count for an MCP. Even for a complex application like Blender, this number is extreme and will overwhelm the agent's context and selection process, likely degrading performance.

    Completeness4/5

    The tool surface is extremely broad, covering animation, rigging, sculpting, retopology, UV, simulation, tracking, compositing, materials, and more. Minor gaps exist (e.g., general object creation without mesh/curve/text separation, no dedicated world settings tool), but the core workflow areas are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources