A
licenseNot graded
qualityB
maintenanceMCP server that enables AI agents to control Google Flow for image and video generation using your own Google account.
59 npm
1
MIT
google-flow-mcp
by LeoSzn12
Related Servers
Alternatives to google-flow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceMCP 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
- AlicenseAqualityBmaintenanceMCP server for generating images via Google Flow's API without daily quota limits, supporting text-to-image and image-to-image generation.11MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI agents to generate images and videos through Google Flow using models like Veo and Nano Banana, with tools for image generation, upscaling, video creation, character management, and music generation.7-
- AlicenseBqualityCmaintenanceA brand-neutral, self-hostable MCP server for generating and editing images using natural language, with support for reference images and multiple providers.1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for generating images and videos using Google Gemini and VEO models, with support for multiple AI models and credential modes.33 PyPI1Apache 2.0
TDQS
B3.4/5.0
Scored across 22 tools
Disambiguation3/5
While most tools target distinct actions, several image/video generation tools (generate_image, batch_generate_images, generate_with_face, generate_from_dossier) overlap in the core generation action and could cause misselection. Storyboard generation also overlaps with the trailer script tool. However, the descriptions do differentiate inputs and use cases.
Naming Consistency4/5
Tool names predominantly follow a verb_noun pattern (e.g., generate_image, list_projects, update_custom_tool). Minor variations like generate_with_face, generate_from_dossier, and save_media_to_local_folder deviate but remain readable and predictable.
Tool Count3/5
At 22 tools, the server is on the heavier side of the recommended range. The breadth is justified by the mix of generation, character/dossier management, custom tool operations, and trailer workflow, but it still feels slightly over-scoped.
Completeness4/5
The tool surface covers the core media generation lifecycle, including account management, image/video generation, upscaling, character consistency, dossier-based generation, custom tool management, and media retrieval/saving. Missing operations are primarily deletion (e.g., no delete_character or delete_media) and character listing, but these are minor gaps.
Maintenance
ActivitySlowing
ResponsivenessNo issues