Skip to main content
Glama

Related Servers

Alternatives to video-atelier-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to edit talking-head videos locally by transcribing footage, applying validated edit operations like cutting fillers and silences, adding zooms, captions, looks and branding, and checking results with rendered previews. Agents can also read pinned editor feedback notes with annotated frames, resolve them, and export MP4, SRT or OTIO while the user watches changes live.
      52 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables chat-driven video editing by letting an MCP host analyze raw clips and produce finished, beat-synced montages with matched music, subtitles, transitions, and picture-in-picture, all previewed as a timeline digest before rendering. It runs locally through agents such as Claude Code, Codex, Hermes, and OpenCode.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Gives coding agents a local FFmpeg video-editing engine exposed over MCP, enabling them to probe, cut, join, reframe, caption, normalize audio, and verify the resulting media without cloud services or API keys. Every operation returns structured JSON and self-checks its own output against delivery specs.
      6,919 npm
      MIT

    TDQS

    C2.7/5.0

    Scored across 49 tools

    Disambiguation3/5

    Tools are grouped by domain and mostly have clear purposes, but several clusters overlap: media_thumbnail/media_extract_frames/export_thumbnail_set all extract images, multiple sam2_* tools perform mask-related operations, and export_formats/clip_format_convert/export_meta have fuzzy boundaries. The descriptions help, but an agent could still misselect among them.

    Naming Consistency4/5

    The dominant pattern is a domain prefix plus an action (media_, captions_, audio_, render_, comp_, clip_ mostly use verb_noun forms), which is readable and predictable. Minor deviations like media_thumbnail (noun), health_check (no prefix), and export_meta (not a clear verb) break the pattern slightly but do not cause major confusion.

    Tool Count2/5

    49 tools is a very large surface for an MCP server. Even though the domain is broad, the count exceeds the 25+ threshold and creates significant selection overhead; many tools could be consolidated (e.g., media_thumbnail versus export_thumbnail_set). The scope feels heavy rather than well-scoped.

    Completeness3/5

    The server covers a wide arc: import, probe, composition, audio, captions, rendering, export, generation, and sam2 segmentation. However, editing workflows are asymmetrical: comp_add_clip/add_overlay/add_transition have no corresponding remove/update tools, media_import has no delete/cleanup, and audio_add_track lacks a removal counterpart. These gaps are noticeable but can sometimes be worked around.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues