google-flow-mcp
Related Servers
Alternatives to google-flow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables users to generate images and videos on Google Flow through browser automation of an already signed-in Chrome session, downloading the finished media to disk without any API keys. It drives Flow's agent with a range of image and video models, plus reference images, first/last frames, and ingredient-based video jobs, while reusing the user's own Google AI Pro credits.17MIT
- AlicenseAqualityDmaintenanceEnables AI agents to drive Google Flow through a real Chrome profile to generate images, videos, characters, and scenes without sharing credentials.41916 npm2MIT
- AlicenseAqualityBmaintenanceLets an AI agent drive Google Flow (flow.google.com) through a locally logged-in Chrome profile to generate images, videos, characters, and scenes. Uses browser automation via the Chrome DevTools Protocol, so Google credentials are never shared with the agent.2116 npmMIT
- AlicenseAqualityBmaintenanceEnables AI assistants to generate and edit images, create Veo and Omni videos, upscale media, and interact with Google Flow's creative agent by driving a Chrome window signed in to the user's own Google account, using their existing plan and credits with no API key and with credit-spend safeguards.18298 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables generating images and videos in Google Flow through an automated browser session using your Google AI Pro subscription, without API keys or third-party credit fees.115 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables generating images and videos on Google Flow through browser automation using your Google AI Pro subscription, with image generation free and video consuming Flow credits.115 npm1MIT
TDQS
Scored across 4 tools
Each tool maps to a distinct step in a linear pipeline (connect/sign-in, read options, generate, download), so misselection is unlikely. The one soft overlap is that flow_generate_images can also download when given download_size, duplicating part of flow_download_images' purpose.
All names share a clear flow_ prefix in snake_case, and three of four follow a verb_noun pattern (get_options, generate_images, download_images). flow_status deviates by omitting the verb, a minor inconsistency against an otherwise predictable scheme.
Four tools is a tight, purposeful set matching a narrow browser-automation workflow, with no filler tools. It sits at the low edge of the comfortable range, but each tool earns its place as a pipeline stage.
The happy path (status, options, generate, download) is fully covered with no dead ends for a straightforward generation run. Minor gaps exist around recovery and discovery: no way to list existing projects/media ids or re-check an in-flight generation, so a timed-out generate leaves the agent with no fallback.