Skip to main content
Glama
mgi24

Blender MCP (Fork)

by mgi24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Blender MCP (Fork)

No user-submitted related servers found.

    Related Servers

    • Blender MCP

      ageless-h
      A
      license
      A
      quality
      D
      maintenance
      MCP server for AI-assisted Blender automation, providing layered tools for perception, declarative and imperative writing, and fallback operations.
      29
      44 PyPI
      5
      MIT

    • Blender MCP

      tattooinmtl
      A
      license
      Not graded
      quality
      C
      maintenance
      This server enables natural language control of Blender 5.2 LTS through any MCP client, allowing scene inspection, object and material manipulation, rendering, and safe Python execution.
      1
      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-mcp

      ceeyang
      A
      license
      C
      quality
      B
      maintenance
      Enables controlling local Blender 5.2 through natural language, providing 159 tools for modeling, materials, shaders, lighting, animation, cameras, rendering, import/export, UV, geometry, rigging, assets, and more via an MCP server.
      159
      1
      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

    B3.4/5.0

    Scored across 22 tools

    Disambiguation3/5

    Tools cluster into clear provider groups (Polyhaven, Sketchfab, Hyper3D, Hunyuan3D), but within 3D generation, generate_hyper3d_model_via_text, generate_hyper3d_model_via_images, and generate_hunyuan3d_model are near-interchangeable from an agent's perspective, differing only by backend service. The parallel poll/import pairs are distinguishable mostly because of naming luck, and set_texture's relationship to download_polyhaven_asset is ambiguous.

    Naming Consistency4/5

    Consistent snake_case verb_noun pattern and a clear provider-prefix convention (polyhaven_, sketchfab_, hyper3d_, hunyuan3d_) makes the set predictable. Deviations include set_texture (drops the provider prefix) and the inconsistent modifier ordering of import_generated_asset_hunyuan vs the pattern used elsewhere, which slightly breaks parallel structure.

    Tool Count3/5

    At 22 tools, the server is on the heavy side—reasonable given that it covers four asset providers plus scene introspection, but it exceeds the ideal 15-tool ceiling. The repeated status-poll-import triads across three generation backends inflate the count without adding conceptual surface area.

    Completeness3/5

    Each provider's core lifecycle is covered (status check, search, download/import for asset libraries; generate, poll, import for gen-AI models), and get_viewport_screenshot provides useful scene feedback. Gaps include no way to enumerate previously downloaded Polyhaven textures despite set_texture requiring a downloaded ID, no cancellation/list of active jobs, and execute_blender_code serving as an awkward catch-all for anything outside the defined tools.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources