Skip to main content
Glama
thanhdoancong127

blender-mcp

by thanhdoancong127
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to blender-mcp

No user-submitted related servers found.

    Related Servers

    • blender-mcp

      Mishaadevv
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to drive a live Blender session for modeling, shading, lighting, rendering, and scene manipulation, returning rendered images for visual feedback.
      122
      MIT

    • mcp-for-maya

      Xxx91n
      A
      license
      A
      quality
      A
      maintenance
      Gives LLM agents spatial awareness inside Autodesk Maya, enabling scene inspection and measurement, aesthetic and engineering audits, camera planning, checkpoint/rollback safety, asset import, and viewport or render previews. Agents can also execute arbitrary Python in Maya to build and verify 3D scenes against engineering rules instead of writing blind.
      25
      465 PyPI
      2
      MIT

    • blender-compact-mcp

      mohakmalviya
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to inspect, discover, and execute batched Blender operations, capture renders/previews, and run arbitrary Python scripts for full bpy workflows, with on-demand operation discovery and bounded payload summaries.
      4
      6
      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.5/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools target clearly distinct operations, and the render family (blender_turntable, blender_render, blender_render_scene) is carefully differentiated by camera source. The pose tools (blender_set_pose vs blender_pose_aim) overlap slightly, but descriptions explicitly state when to prefer each.

    Naming Consistency5/5

    Every tool uses the same blender_ snake_case prefix, and names read as clear verb_noun or noun_noun constructs. Minor verb-placement variation (blender_render_scene vs blender_scene_info) does not break the pattern.

    Tool Count4/5

    25 tools is on the heavy side, but the surface genuinely spans several subdomains (file/lifecycle, rendering, rigging/posing, validation). Each tool maps to a distinct capability rather than redundant variants.

    Completeness4/5

    The set covers lifecycle (start/stop/status, open/save/new), import/export, scene/object inspection, rendering, rigging/posing/keyframing, and validation/comparison. Gaps like direct object deletion or material editing exist but are largely workable via blender_run_python.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources