Skip to main content
Glama

Related Servers

Alternatives to Pavo 官网 MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      An MCP server that exposes Tripo Studio operations as structured tools over stdio, letting agents generate, edit, animate, and manage images, 3D models, textures, projects, and Canvas assets through the user's own Studio web account. It also covers task inspection, downloads, and batch workflows without requiring a developer API key.
      176
      989 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables external AI clients to automate and inspect Pencil2D through MCP, including authenticated sessions, layers, keyframes, strokes, undo/redo, previews, saves, snapshots, and export jobs.
      GPL 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search, browse, download, organize, and post-process comics through MCP tools, including account login, favorites, comments, rankings, configuration, and download task control. Supports stdio, SSE, and HTTP transports while exposing knowledge resources for configuration and skill reference.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables any MCP-compatible AI agent to generate videos and images from text or reference frames, chain scenes into seamless multi-scene films with sound and speech, and download finished media with manifests and previews. It also exposes account status, plan limits, history and library management through confirm-gated, safe-by-default operations.
      26
      34
      MIT

    TDQS

    B3.4/5.0

    Scored across 57 tools

    Disambiguation3/5

    The set splits into two parallel universes (canvas/graph editing under pavo_* and AI script production under pavo_script_*) that both contain projects, assets, models, and tasks, so pairs like pavo_get_project vs pavo_script_get_project, pavo_list_assets vs pavo_script_get_assets, or pavo_get_task vs pavo_script_get_segment_video_task rely almost entirely on the prefix to disambiguate. Within script, three overlapping creation entry points (create_ai, import_text, import_file, plus upload_file as a preparatory step) create residual ambiguity, though the very detailed descriptions do spell out the intended boundaries.

    Naming Consistency4/5

    Names follow a stable pavo_[script_]verb_noun convention (get_/list_/create_/update_/delete_/submit_/apply_/attach_/select_/save_/set_/download_), which is highly predictable across 57 tools. Minor deviations exist, e.g. pavo_server_status and pavo_auth_import_authorization, and the script_ prefix is a namespace rather than a verb, but overall the pattern is readable.

    Tool Count2/5

    57 tools is far beyond a practical agent-facing surface, even for a genuinely broad product covering canvas graphs plus a full script-to-video pipeline. Many operations are fine-grained (separate tools for creating a storyboard segment vs a shot, setting a main image vs a four-view image), pushing complexity onto the caller rather than consolidating via parameters.

    Completeness4/5

    Coverage of the domain is unusually deep: project/canvas lifecycle, node CRUD, connections, model constraints, templates, validation, task submission/status/sync/download, plus script creation, outline, episodes, assets and their states/images, storyboard segments/shots, media attach/select and video submission. Notable gaps remain around destructive/lifecycle ends: no delete for projects, nodes, connections, or script assets, and no task listing or cancellation tool.