Skip to main content
Glama

Related Servers

Alternatives to Remote Blender MCP

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI clients to control a running Blender instance through the Model Context Protocol, allowing scene inspection, object creation and editing, rendering, and execution of Blender Python. It works locally via a WebSocket bridge between the MCP server and a Blender add-on.
      15
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables remote control of Blender via the Model Context Protocol, allowing users to execute Python scripts, query scene data, and generate 3D models from images. It provides a bridge for AI clients to interact directly with Blender's internal environment and automate 3D content creation.
      3
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to drive a live Blender session over MCP by creating and transforming primitives, building and assigning materials, inspecting scenes and objects, capturing viewport screenshots, and executing arbitrary bpy Python. Commands are relayed over a local TCP bridge to a Blender add-on and executed on Blender's main thread, supporting multiple simultaneous AI clients.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable AI clients to control a local Blender workstation through a secure HTTP gateway for 3D scene inspection, modeling, rigging, animation, materials, rendering, import/export, and controlled Python automation. Supports permission profiles and authentication modes to keep Blender execution local while allowing AI-assisted production workflows.
      1
      MIT

    TDQS

    B3.1/5.0

    Scored across 26 tools

    Disambiguation4/5

    The tools mostly target distinct resources and actions, and the descriptions clarify overlaps. The main gray areas are the cluster of inspect_* tools (scene/object/nodes/dependencies), which are separable by description but could be mistaken for one another, and the render vs viewport_screenshot vs view_image trio, which requires reading the descriptions to keep straight.

    Naming Consistency4/5

    Nearly all tools follow a snake_case verb_noun pattern (list_sessions, inspect_object, run_operator, save_project, upload_file). A few deviations exist: noun-first names like session_status and job_status, the noun_noun viewport_screenshot, and the bare verb render. Still largely readable and consistent.

    Tool Count3/5

    26 tools is at or above the heavy threshold, but the scope is genuinely broad—sessions, jobs, multiple inspection types, execution, rendering, checkpoints, and file IO. Each tool maps to a distinct operation, yet the surface is on the large side and some inspection tools could potentially be consolidated.

    Completeness4/5

    Coverage is strong across the full lifecycle: session management, job control, scene/object/node inspection, arbitrary execution, rendering, checkpoints, and file transfer. Minor gaps exist—e.g., no file delete/move and no explicit checkpoint deletion—but core workflows are fully covered.