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 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.4MIT
PixVerse MCPofficial
AlicenseNot gradedqualityFmaintenanceEnables video generation from text, images, and more through MCP-compatible apps like Claude and Cursor.52MIT- 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.1323,846 npmMIT
- AlicenseNot gradedqualityCmaintenanceExposes video generation and editing tools to MCP-capable clients, enabling text-to-video, image-to-video, video editing, reusable voice and character profiles, and task status queries through natural language.4MIT
Popcraft MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to generate and edit video, images, 3D, music, and sound effects, upload or reuse media, preview credit costs, and follow production workflows through a single hosted connector.MIT
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
ActivityMaintained
ResponsivenessNo issues