A
licenseNot graded
qualityC
maintenanceEnables 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.
83 npm
2
MIT
flow-mcp
by parthmax2
Related Servers
Alternatives to flow-mcp
No user-submitted related servers found.
Related Servers
- 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.83 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to drive Google Flow through a real Chrome profile to generate images, videos, characters, and scenes without sharing credentials.4194 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.214 npmMIT
- AlicenseNot gradedqualityCmaintenanceLets AI agents generate images in Google Flow by driving the real web app in a Chrome window you sign into once, selecting the model, aspect ratio, and image count from a prompt. Results can be downloaded at 1K, 2K, or 4K, all without an API key.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to generate Google Flow videos and images and automate Scene Builder clip extensions through a user's own Chrome session.1166 npm6MIT
TDQS
A3.9/5.0
Scored across 18 tools
Disambiguation4/5
Most tools map to a distinct resource or step (status, sign-in, credits, projects, assets, trash, characters, settings, wait, approve), and descriptions explicitly disambiguate tricky pairs like generate_video vs. flow_chat/flow_approve and generate_image vs. generate_images. The only real friction is the intentional overlap between the video shortcut and the chat+approve workflow, plus the single-vs-batch image pair, which an agent must read carefully to choose correctly.
Naming Consistency3/5
Almost all tools carry the flow_ namespace prefix, which is predictable, but the pattern is not verb_noun: several are bare nouns (flow_status, flow_credits, flow_projects, flow_settings) while the core generation tools break the namespace entirely (generate_video, generate_image, generate_images). Readable, but the convention is mixed rather than uniform.
Tool Count4/5
18 tools is on the heavy side but each covers a genuinely separate part of driving a browser-based generation service (auth, credits, assets, generation, approval, polling, cleanup). Nothing looks redundant enough to cut, though a few convenience wrappers (flow_frame, flow_capabilities) push it slightly past a tight scope.
Completeness4/5
The lifecycle is well covered: health check, sign-in, credits, project listing, image/video generation, batch generation, upscaling, asset listing, trash with confirmation, characters, settings, chat/approve/poll and frame extraction. Gaps are minor but real: no project create/rename/delete, no character deletion action, and no direct asset download except through upscale or wait.
Maintenance
ActivityMaintained
ResponsivenessNo issues