google-flow
Related Servers
Alternatives to google-flow
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents to orchestrate Google Flow video and image generation, including multi-scene planning, silent background generation, credit tracking, and video stitching via MCP.25MIT
- AlicenseBqualityDmaintenanceMCP server that lets AI agents control Google Flow for generating images and videos using the user's own Google account. It provides tools for image generation, video creation, character and scene management, and UI discovery.171MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to generate and edit Google Flow images and videos, run batch storyboards, manage projects and characters, check credits, and download 1080p clips through a signed-in Flow account.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents from an MCP client to control Google Flow through a signed-in Chrome session, generating videos and images with Veo, Nano Banana, and Omni while managing projects, assets, scenes, characters, and shot lists with spending-approval guards and a sandboxed file vault.5MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that enables AI agents to control Google Flow for image and video generation using your own Google account.119 npm1MIT
- AlicenseCqualityCmaintenanceEnables agents to run durable video and image generation jobs through the user's own signed-in Google account, with idempotent job tracking, automatic quality-check and finishing, and delivery-ready local files. Also exposes browser session control and Google Workspace tools (Gmail, Drive, Sheets, Docs, Calendar) over MCP.45MIT
TDQS
Scored across 3 tools
flow_status is clearly a connection/auth check, while generate_image and generate_video are distinct media generation operations with no overlap in intent. An agent can confidently separate status verification from content creation.
generate_image and generate_video follow a consistent verb_noun pattern, but flow_status breaks the convention by leading with the noun and using a different style. The mixed pattern is readable but not fully uniform.
At 3 tools, the surface is small but appropriately scoped for a focused media generation server. Each tool serves a distinct purpose and there is no bloat, though the set could slightly expand to cover more workflow steps.
The core generation capabilities for images and videos are present, and the status check covers connection state. However, there are notable gaps: no way to list, retrieve, cancel, or manage generation jobs/results beyond local saving.