A
licenseA
qualityB
maintenanceEnables AI agents to generate Google Flow videos and images and automate Scene Builder clip extensions through a user's own Chrome session.
11
66 npm
8
MIT
autoflow-mcp
Officialby inov8ing
Related Servers
Alternatives to autoflow-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityDmaintenanceEnables AI agents to drive Google Flow through a real Chrome profile to generate images, videos, characters, and scenes without sharing credentials.41912 npm2MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to automate a local background Chromium browser for interactive web tasks, including prompt generation on Google Flow (Veo & Imagen), DOM inspection, clicks, screenshots, and JavaScript evaluation.8MIT
- 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
- 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.119 npm1MIT
TDQS
A3.8/5.0
Scored across 11 tools
Disambiguation4/5
Each tool targets a distinct action: status, generation, queue management, troubleshooting, and inspection. The only slight overlap is between clear_queue and cancel, but they differ in scope (clearing all pending vs. canceling any running/queued job). All others are clearly separated.
Naming Consistency4/5
Tools follow a consistent 'autoflow_' prefix with verb-noun patterns like get_recent_assets, clear_queue, and capture_screenshot. However, 'autoflow_status' uses a noun instead of a verb, and there's a mix of 'get_' and 'list_' prefixes, which is a minor deviation.
Tool Count5/5
11 tools is well-scoped for a specialized server focused on AI generation management in Google Flow. Each tool covers a distinct need without redundancy, and the count feels appropriate for the domain.
Completeness4/5
The tool surface covers the core lifecycle: generation, queue inspection/control, troubleshooting (heal/reload), and visual verification (screenshot). Minor gaps exist like asset management or project editing, but the essential workflows are complete.