Skip to main content
Glama
Sign In
BeatDesign

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.
      2
      AGPL 3.0

    • MCP Video Gen

      the-code-learner
      A
      license
      Not graded
      quality
      B
      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
      D
      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 38 tools

    Disambiguation3/5

    Most tools map to a distinct domain+action, but several boundaries blur: bdesign_editor_import_srt overlaps with bdesign_editor_edit (whose description already lists SRT import), and bdesign_generation_models vs bdesign_generation_model_get, bdesign_project_open vs bdesign_project_target, and the four view/handoff tools (project_open, canvas_view, editor_view, project_target) are easy to confuse. The multiple *_apply tools (organization, canvas, workflow_template) are separable by description but require careful reading.

    Naming Consistency4/5

    A predictable bdesign_<domain>_<action> pattern holds across nearly all 38 tools (project_list/get/create, asset_list/get/import, canvas_get/apply/search). Minor deviations like bdesign_generation_models (list without a verb) and a few compound verbs (continue_from_tail, extract_frame, import_srt) break the pattern slightly but remain readable.

    Tool Count2/5

    38 tools is heavy even for a multi-surface creative app (project, asset, canvas, editor, generation, organization, workflow, skills). Several micro-tools such as generation_model_get, canvas_search, and editor_snapshot could plausibly fold into neighbors, making the surface feel enumerated rather than curated.

    Completeness4/5

    Lifecycle coverage is broad: project create/read/update/open, asset import/query/extract, canvas read/apply/search, full editor edit/render/history/diagnostics, generation submit/status/history, workflow templates preview/apply. Gaps are minor—no asset or project delete, no generation cancel—and likely recoverable from the shared command kernel.

    Maintenance

    ActivityActive
    ResponsivenessMixed handling

    Resources