Skip to main content
Glama

Related Servers

Alternatives to Modisign 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to build and edit a real video timeline — cuts, text, shapes, keyframes, captions and music — in a live studio the user can watch and edit alongside, rendering actual frames so the agent can verify its own work instead of guessing. Finishes by exporting an MP4 or carrying the timeline into DaVinci Resolve, Premiere Pro, CapCut or Remotion.
      2
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Gives an AI client local control over Adobe Premiere Pro, letting it inspect footage frame-by-frame to find the best moments, assemble and trim edits on the timeline, render animated title cards, review its own work, and export the finished video. Vision and editing tools run entirely on the user's own computer, with nothing sent to the publisher.
      289
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to generate, edit and render finished, ready-to-post videos from a plain-language prompt, including script, visuals, voiceover, captions and music for TikTok, Reels and YouTube. Also supports remaking reference videos, importing your own media, and reviewing or adjusting existing videos before rendering.
      MIT

    TDQS

    A4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: overlay discovery (list/get), configuration, rendering, compositing, video editing, transcription, job lifecycle, and auth. The only potential overlaps—render_overlay vs add_overlay_to_video and add_overlay_to_video vs edit_video—are explicitly clarified by descriptions indicating when to use each.

    Naming Consistency4/5

    8 of 11 tools follow a clear verb_noun pattern (get_overlay, cancel_job, list_overlays, configure_overlay, render_overlay, add_overlay_to_video, edit_video, get_transcript). job_status/account_status use noun_status and login is a bare verb, but these deviations are minor and readable.

    Tool Count5/5

    11 tools is well within the ideal 3-15 range for an overlay/video-editing server. Each tool covers a necessary slice: discovery, configuration, rendering/compositing, editing, transcription, job control, and auth.

    Completeness4/5

    Core workflows are fully covered: overlay search/inspection/configuration/render/composite, comprehensive local video editing with captions, transcription, job status/cancel, and login/account checks. Minor gaps remain (no media metadata probe, no way to list saved overlay configurations, no logout), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues