Skip to main content
Glama

Related Servers

Alternatives to VideoGen MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets MCP clients such as Claude, Cursor, Cline and Windsurf turn a text prompt or a public photo URL into a video clip with a soundtrack, returning a run id and then the finished file's URL, and also checks remaining account credits. Runs locally over stdio via npx or against a hosted Streamable HTTP endpoint using an API key.
      364 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables video generation through OpenAI's Sora 2 API, allowing users to create, monitor, and manage AI-generated videos. It also provides tools for merging video clips and creating fade animations from static images using FFmpeg.
      6
      7 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes one tool per pipeline command so an AI agent can drive the work of turning audio into a reviewable vertical video draft: importing sources, transcribing with word timings, planning beats, generating one AI image per beat, and rendering a 1080×1920 MP4 with word-synced captions. Paid steps stay gated behind script approval given from the CLI, so agents can run the loop for Reels, TikTok and YouTube Shorts without overspending.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets assistants like Claude, ChatGPT, and Gemini CLI generate videos and images in Google Flow using your own signed-in account and credits, with no API key required. It automates the Flow website to run text-to-video, frames-to-video, reference-guided, and storyboard workflows, plus optional Gemini API tools for extending or editing clips.
      MIT

    TDQS

    B3.4/5.0

    Scored across 49 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is some overlap: script_to_video, storyboard_to_video, voiceover_to_video, and slideshow_to_video all produce editable videos from different inputs, requiring careful description reading to choose correctly. The guidance tools (get_*_guidance) also overlap somewhat but are clearly differentiated by topic.

    Naming Consistency4/5

    Naming is mostly consistent with snake_case verb_noun or noun_verb patterns (generate_image, list_projects, get_project, upload_file, create_entity), though some deviations exist like storyboard_to_video, script_to_video (noun_to_noun) and guidance tools prefixed with get_. Still generally predictable and readable.

    Tool Count2/5

    49 tools is excessive for the apparent scope of a video generation API, even accounting for the broad domain (workflows, media generation, files, entities, projects, account). Many tools could be consolidated or grouped, making the surface heavy and increasing selection difficulty.

    Completeness4/5

    Coverage is quite comprehensive: creation, listing, getting, updating, archiving, uploading, guidance, and export for projects, workflows, tool executions, files, and entities. Minor gaps exist (e.g., no direct delete for projects/files, no update for file metadata), but core lifecycle operations are present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues