Skip to main content
Glama
djeada

Blender MCP Server

by djeada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Blender MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • Blender MCP

      tattooinmtl
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP client to control Blender 5.2 LTS via natural language, including scene creation, object manipulation, material assignment, rendering, and Python execution.
      1
      MIT

    • BlenderMCP

      clanker25
      A
      license
      A
      quality
      C
      maintenance
      Enables connecting Blender 3D to AI assistants via MCP, allowing prompt-driven 3D modeling, scene editing, and real-time manipulation. Supports object/material control, scene inspection, viewport screenshots, and integrations with Poly Haven, Sketchfab, and AI model generators.
      22
      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.6/5.0

    Scored across 27 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear separation between scene, object, material, render, export, history, Python execution, and job management. Even potentially overlapping tools like blender_python_exec vs. blender_python_exec_async are explicitly differentiated by sync vs. async behavior.

    Naming Consistency4/5

    All tools use the blender_ prefix and snake_case, with predictable domain/action naming. Minor ordering deviations exist (e.g., blender_render_still vs. blender_scene_get_info), but the overall pattern remains highly readable.

    Tool Count4/5

    27 tools is slightly above the typical 3-15 range, but Blender is a broad domain and each tool covers a specific, useful operation. No tool feels redundant or trivial, though some consolidation (e.g., separate export formats) could reduce the count.

    Completeness4/5

    The surface covers core Blender automation: object creation/transform/duplication, material creation/assignment, rendering, export, history, and Python execution. Minor gaps like material deletion or scene save/load are not directly exposed, but the asynchronous Python execution tool can fill those gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources