gflow-cli
Related Servers
Alternatives to gflow-cli
No user-submitted related servers found.
Related Servers
- 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.5282 npmMIT
- 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 npm68MIT
- 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.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.27MIT
- AlicenseAqualityBmaintenanceEnables AI agents to drive Google Flow through a real Chrome profile to generate images, videos, characters, and scenes without sharing credentials.1913 npmMIT
- AlicenseAqualityAmaintenanceEnables AI agents to generate Google Flow videos and images and automate Scene Builder clip extensions through a user's own Chrome session.11497 npmMIT
TDQS
Scored across 15 tools
Most tools are clearly distinct by resource and action (auth, instructions, generation, characters, projects, credits). The only mild overlap is gflow_character_list vs gflow_character_show (list vs show one) and the instructions family, but each has a distinct purpose.
Tool names consistently use a gflow_ prefix followed by a noun or noun_verb pattern (e.g., gflow_character_list, gflow_instructions_add). Minor inconsistency: gflow_list_tools and gflow_list_projects use list_ before the noun, while others use noun_list, but the pattern is still predictable.
15 tools is at the upper edge of the well-scoped range, but each tool maps to a distinct operation across auth, generation, characters, projects, and instructions. The count is justified by the breadth of the domain, though it feels slightly heavy.
The surface covers core workflows: auth check, credit check, project listing, image/video generation, character discovery, and full CRUD-like lifecycle for instruction cards. Minor gaps: no tool for creating/deleting characters or projects, and no explicit tool for listing generation history, but agents can work around these.