A
licenseA
qualityD
maintenanceEnables AI agents to drive Google Flow through a real Chrome profile to generate images, videos, characters, and scenes without sharing credentials.
4
19
9 npm
2
MIT
google-flow-mcp
by ParkSangGwon
Related Servers
Alternatives to google-flow-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 gradedqualityBmaintenanceEnables AI coding agents to autonomously generate images, music, and cinematic video directly from their coding environment by connecting to Google Labs and Google Flow through the user's Chrome session.3MIT
- 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
- AlicenseAqualityFmaintenanceControls 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.1817130 npm121MIT
- 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.130 npm2MIT
TDQS
A4/5.0
Scored across 11 tools
Disambiguation5/5
Each tool addresses a distinct part of the workflow: connection/status, page observation, project opening, generation, media download, and scene operations. Similar actions like generating a video versus extending a scene are clearly separated by context and dedicated names.
Naming Consistency3/5
All tools share a useful flow_ prefix and consistent snake_case, but the word order is mixed: flow_generate_video is verb-object while flow_project_open, flow_media_download, and flow_scene_add are object-verb. This is still readable but does not follow a single predictable verb_noun pattern.
Tool Count5/5
Eleven tools is well-scoped for the Google Flow domain, covering browser connection, inspection, project navigation, generation, downloads, and scene extension without redundancy. Each tool earns its place and the count is within the ideal range.
Completeness4/5
The core end-to-end workflows are covered: connect, open a project, generate video/image with confirmation and resume support, download media, and extend scenes. Minor gaps exist around enumerating projects or arbitrary media IDs without a prior URL or generation result, but these are workable.
Maintenance
ActivityStale
ResponsivenessUnresponsive