Skip to main content
Glama
Sign In
ABOOAI

hunyuan-workbench

by ABOOAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hunyuan-workbench

No user-submitted related servers found.

    Related Servers

    • 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

    • Blender Open MCP

      YenCruz79
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a live Blender session, including scene and object operations, rendering, and PolyHaven asset workflows. Supports provider-agnostic LLM backends that can be switched at runtime through MCP tools.
      -

    • Blender Open MCP

      Alvarez868
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to control a live Blender session through MCP tools for scene and object manipulation, rendering, PolyHaven asset search/download/texturing, and guided scene workflows, while allowing runtime switching between local or OpenAI-compatible LLM providers.
      -

    • Blender Open MCP

      Riccardo762
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive a live Blender session over MCP by inspecting scenes, creating and modifying objects, assigning materials, rendering images, and fetching PolyHaven assets. It also exposes prompt-based scene building and review workflows backed by a provider-agnostic LLM layer (Ollama, LM Studio, llama.cpp, OpenAI-compatible endpoints, Azure) that can be switched at runtime.
      -
    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/5.0

    Scored across 19 tools

    Disambiguation2/5

    Multiple read/state tools (list, get, status, watch, watches, browser_result, doctor) have overlapping 'read local state or monitoring results' purposes, and browser_run vs submit can both lead to generation. The descriptions do help distinguish them, but an agent still faces several near-boundary choices.

    Naming Consistency3/5

    All tools share the workbench_ prefix and snake_case, which gives a readable family feel. However, the naming convention is mixed: some are verb_noun like browser_start and prepare_feature, while others are bare nouns or verbs like list, get, watches, assets, capabilities, and doctor.

    Tool Count3/5

    At 19 tools, the server is in the borderline-heavy range. Most tools map to a real workflow stage, but several status/watch/result variants could likely be consolidated.

    Completeness4/5

    The server covers the core generate-monitor-download-archive lifecycle, including recovery, manual ingest, diagnostics, and basic Blender integration. Minor gaps exist around cancellation and cleanup/delete operations, but the intended workflow has no obvious dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources