Google Flow Browser MCP
Related Servers
Alternatives to Google Flow Browser MCP
No user-submitted related servers found.
Related Servers
- 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.219 npmMIT
- 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.130 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to generate Google Flow videos and images and automate Scene Builder clip extensions through a user's own Chrome session.1166 npm8MIT
- AlicenseAqualityAmaintenanceEnables AI agents to programmatically generate images and videos through the authenticated Google Flow web interface via a direct Chrome DevTools Protocol connection, exposing tools for media generation, project management, status checks, and asset downloads without requiring official API keys.276MIT
- AlicenseAqualityDmaintenanceEnables AI agents to drive Google Flow through a real Chrome profile to generate images, videos, characters, and scenes without sharing credentials.4199 npm2MIT
- 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.18471 npmMIT
TDQS
Scored across 17 tools
Most tools have distinct purposes (connection, character/scene management, generation, UI), but flow_generate_image and flow_generate_video could be confused if descriptions are skimmed. flow_use_tool is generic but still differentiated.
All tools follow a strict 'flow_verb_noun' pattern with snake_case, e.g., flow_create_character, flow_generate_image. Naming is highly consistent and predictable.
17 tools is appropriate for the scope of browser automation over Google Flow, covering connection, state management, content creation, and generation. Slightly on the higher side but well-justified.
Core CRUD for characters (create, import, list) but missing update/delete. No tools for scene management beyond creation. Video generation stops before final action, leaving a gap. UI discovery and queue status are nice extras.