OmniFlow MCP
Related Servers
Alternatives to OmniFlow MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude Code and Claude Desktop to drive Dreamina's Seedance 2.5 for batch video generation, including cinematic techniques, references, first/last frames, video-to-video edits, and automatic clip downloads via the SeedFlow Chrome extension.513 npmMIT
- AlicenseAqualityAmaintenanceDrives Google Flow from an agent or the terminal: Veo text-to-video, image-to-video and clip extension, plus Imagen image generation. Runs locally against your own Google account with Flow access; video generation bills that account's credits.161,499 PyPI222MIT
- AlicenseAqualityAmaintenanceEnables AI agents to generate Google Flow videos and images and automate Scene Builder clip extensions through a user's own Chrome session.1165 npm1MIT

autoflow-mcpofficial
AlicenseAqualityBmaintenanceEnables AI agents to command browser-based AI generation models (like Imagen 3, Omni Flash, Veo 3) through the Autoflow Chrome Extension, with background queueing for autonomous media generation.119 npmMIT- AlicenseAqualityDmaintenanceControls Google Flow for image and video generation from an AI agent. Enables generating images with models like Imagen 4, creating videos, managing characters and scenes via browser automation.1785 npm74MIT
- AlicenseAqualityDmaintenanceEnables AI agents to drive Google Flow through a real Chrome profile to generate images, videos, characters, and scenes without sharing credentials.199 npmMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: status checks connection/state, generate queues new work, edit modifies finished videos, wait polls for completion, and cancel removes queued work. Even though generate and edit both ultimately produce jobs, their descriptions make the different input contexts unambiguous.
All tools follow the same flow_ prefix with a single descriptive verb or noun suffix: status, generate, edit, wait, cancel. This creates a predictable and easy-to-navigate naming scheme.
Five tools is a tight, well-scoped set for an OmniFlow generation/editing bridge. Each tool maps to a necessary stage in the workflow without redundant or filler tools.
The core lifecycle is covered: check status, generate, edit, wait, and cancel queued jobs. Minor gaps exist such as no explicit way to cancel an in-progress job or list finished job history, but these are workable for the primary use case.