A
licenseC
qualityB
maintenanceEnables AI agents to orchestrate Google Flow video and image generation, including multi-scene planning, silent background generation, credit tracking, and video stitching via MCP.
25
MIT
google-flow-mcp
by RohaanA
Related Servers
Alternatives to google-flow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseBqualityCmaintenanceEnables any MCP-compatible AI agent to generate videos and images from text or reference frames, chain scenes into seamless multi-scene films with sound and speech, and download finished media with manifests and previews. It also exposes account status, plan limits, history and library management through confirm-gated, safe-by-default operations.2634MIT
PixVerse MCPofficial
AlicenseNot gradedqualityDmaintenanceEnables video generation from text, images, and more through MCP-compatible apps like Claude and Cursor.55MIT- AlicenseAqualityBmaintenanceEnables any MCP client such as Claude, Cursor, Cline or Gemini CLI to generate Seedance 2.5, Seedance 2.0, MiniMax H3 and Veo 3.1 videos and still images from text or a reference image using your own account. It also exposes run-status polling and remaining-credit checks, with configurable duration, resolution, aspect ratio and audio.453 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to take a raw script all the way to a finished, downloadable short-drama .mp4, covering AI rewrite, character consistency, storyboards, frames, video shots, TTS voiceover, and final cut with quote-before-spend billing from any MCP client.1325,755 npmMIT
TDQS
C2.8/5.0
Scored across 23 tools
Disambiguation4/5
The tools largely target distinct resources and actions: generation vs editing vs status vs media retrieval are clearly differentiated by descriptions. There is minor potential overlap between agent-driven generation (flow_agent_chat) and direct generation (flow_generate_video/image), but the agent interface is presented as distinct. Overall, an agent should be able to select the right tool without much confusion.
Naming Consistency4/5
All tools use a consistent flow_ prefix and snake_case, with a clear verb_noun pattern for most tools (list_models, create_project, generate_video). Slight deviations like flow_status and flow_video_status (noun-first) and the agent tools (flow_agent_respond, flow_agent_chat) break the verb_noun pattern, but the naming remains predictable and readable.
Tool Count3/5
23 tools is on the heavy side for a Flow client, covering many aspects of project, character, scene, media, and agent management. While each tool addresses a distinct need, the count falls in the borderline heavy range (16-25), which may increase cognitive load for agents. A slightly leaner surface would likely be more effective.
Completeness4/5
Core workflows for projects, characters, scenes, media, generation, and agent interaction are well covered. However, deletion operations (project, character, scene) and project update are missing, and flow_list_models only lists video models, leaving minor gaps that agents can likely work around.
Maintenance
ActivitySlowing
ResponsivenessOutdated data