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.
19
6 npm
MIT
google-flow-mcp
by ParkSangGwon
Related Servers
Alternatives to google-flow-mcp
No user-submitted related servers found.
Related Servers
- 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.2MIT
- 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.1765 npm74MIT
- 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.65 npm1MIT
- 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.271MIT
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
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
ActivityMaintained
ResponsivenessNo issues