Skip to main content
Glama
BeatAPI

BeatDesign

by BeatAPI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to BeatDesign

No user-submitted related servers found.

    Related Servers

    • vidcut

      mao-data
      A
      license
      Not graded
      quality
      B
      maintenance
      AI-native timeline editor for short-form video. Your agent cuts, captions, adds motion graphics and renders against a real, editable timeline over MCP — not a render queue. Human-in-the-loop by design: it calls request_review and waits while you supervise in a browser. Local-first and AGPL; your footage never leaves your machine.
      1
      AGPL 3.0

    • MCP Video Gen

      the-code-learner
      A
      license
      Not graded
      quality
      A
      maintenance
      A self-hosted MCP server that connects AI clients to local media-generation backends like ComfyUI and Blender, and provides built-in utilities for video/audio analysis, editing, subtitles, speech, and scene detection via a persistent file cache.
      Apache 2.0

    • CutPilot

      Hellotravisss
      F
      license
      Not graded
      quality
      B
      maintenance
      Local-first AI video editing engine controlled by MCP-compatible AI hosts, enabling AI to inspect footage, propose edits, modify multitrack projects, and render locally while keeping user control.
      -
    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

    C2.9/5.0

    Scored across 29 tools

    Disambiguation4/5

    Tools are grouped by domain and most have clear boundaries. A few overlaps exist: editor_edit already covers SRT import but editor_import_srt duplicates that action, and canvas_get/editor_get can be confused with the view/handoff tools. Overall an agent can usually choose the right tool from the prefix and resource.

    Naming Consistency4/5

    Names consistently use bdesign_<domain>_<action> and snake_case, making navigation predictable. Minor deviations such as generation_models (not generation_model_list) and canvas_continue_from_tail (a phrasal verb) break the strict pattern but do not cause real confusion.

    Tool Count2/5

    29 tools is on the heavy side, and the count is inflated by multiple get/view/history variants across Canvas, Editor, and Generation. While each domain has coverage, an agent faces a large selection surface and several tools could be consolidated or exposed as options within a single tool. This exceeds the comfortable 3-15 range for a well-scoped server.

    Completeness3/5

    Core workflows (project, asset, canvas, editor, generation, skills) are broadly covered, and operations like render, diagnose, and continue-from-tail anticipate real editing needs. However, several lifecycle gaps exist: projects and assets have create/list/get/import but no update/delete, and generation tasks cannot be cancelled. These are workable gaps but represent notable missing operations.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources