gflow-cli
Related Servers
Alternatives to gflow-cli
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables users to generate images and videos on Google Flow through browser automation of an already signed-in Chrome session, downloading the finished media to disk without any API keys. It drives Flow's agent with a range of image and video models, plus reference images, first/last frames, and ingredient-based video jobs, while reusing the user's own Google AI Pro credits.17MIT
- 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
- AlicenseAqualityAmaintenanceEnables Claude to drive Google Flow end-to-end: batch video generation on Veo 3 / Omni 1.1, scene chaining, keyframe transitions, video-to-video edits, and automatic downloads, all through a local bridge with the OmniFlow Chrome extension.5112 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.181783 npm115MIT
- 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
- 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.275MIT
TDQS
Scored across 19 tools
Each tool targets a distinct resource plus action: generation, upscaling, downloading, auth/credits, catalogs, characters, projects, and instruction cards. The instruction tools have clear boundaries: full-sync replace vs incremental add/remove vs per-card enable vs master toggle. Catalog listers are distinguished by resource (tools, models, projects, characters).
All names are snake_case with a gflow_ prefix, but the convention mixes verb-first names (gflow_generate_image, gflow_list_projects) with domain-first names (gflow_character_show, gflow_instructions_apply, gflow_auth_status). It remains readable, but the pattern is not predictable across the set.
The 19 tools are justified by the CLI's broad scope, but 16-25 tools is on the heavy side, especially with six instruction-card tools. Each tool has a role, but the surface is larger than a tightly scoped server would need.
Core media workflows are covered: image/video generation, upscaling, video download, auth, credits, catalogs, characters, and instructions. However, lifecycle gaps remain, notably no character creation tool despite character voice guidance referring to creating characters, and project management is limited to listing. Download is also explicitly video-only, leaving image media retrieval by ID uncovered.