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.525 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.17125 npm81MIT
- 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.125 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.273MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to drive a Google Flow web workspace through local login-session reuse: inspecting the account's actual models and parameters, submitting image and video generation jobs, tracking each job by persistent ID, and downloading the matching media to a specified local path with file and parameter records. Supports repeatable, multi-shot video production workflows where tracked assets are handed off to editing tools like FFmpeg.11MIT
- AlicenseAqualityDmaintenanceEnables AI agents to drive Google Flow through a real Chrome profile to generate images, videos, characters, and scenes without sharing credentials.1914 npmMIT
TDQS
Scored across 16 tools
Most tools target clearly distinct resources or actions: image generation, video generation, character reads, project listing, credits, auth, and instruction management are easy to separate. The only mild overlap is between instruction add/apply and set_enabled/toggle_mode, but the descriptions do explain the differences.
All tool names use a consistent gflow_ prefix and snake_case, with readable, domain-oriented labels. However, the internal ordering is mixed: some are verb_noun (list_projects, generate_image) while domain-specific tools use noun_verb (character_list, instructions_add).
16 tools is slightly above the typical 3-15 sweet spot, but the server spans generation, characters, instructions, projects, credits, auth, and media download. The count is reasonable for that breadth and does not feel bloated.
Generation and instruction CRUD are well covered, but there are notable gaps: no tools to create/update/delete projects or characters, and no asset listing/management despite @AssetName references being central to generation. These omissions limit full lifecycle coverage.