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 MinaSalib216
Related Servers
Alternatives to google-flow-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceSelf-hosted MCP server for Google Flow that enables image and video generation, upscaling, and character consistency through your own Google account.22-
- 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-
- AlicenseAqualityBmaintenanceMCP server for generating images via Google Flow's API without daily quota limits, supporting text-to-image and image-to-image generation.11MIT
- 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
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to control a local ComfyUI instance for image generation, allowing workflow understanding, parameter modification, execution, and model discovery.23 npm3Apache 2.0
TDQS
B3.3/5.0
Scored across 17 tools
Disambiguation4/5
Most tools have clearly distinct purposes, such as connection management, generation, and character/scene creation. Minor overlap exists between flow_status and flow_account_check, and flow_use_tool may overlap with specialized tool openers, but descriptions are sufficient to disambiguate.
Naming Consistency3/5
All tools share the flow_ prefix, but verb styles vary: some use verb_noun (generate_image, create_scene), others are bare verbs (connect, disconnect), and others are noun-first (status, queue_status, account_check). This mixed pattern reduces consistency.
Tool Count4/5
At 17 tools, the count is slightly above the ideal 3-15 range but justified by the breadth of features (connection, generation, characters, gallery, UI automation). The set is not bloated, but a few could be consolidated.
Completeness3/5
The toolset covers major workflows: connect, generate, create characters/scenes, manage queue, and download. However, there are no update/delete operations for characters or scenes, no scene listing, and no way to list all generated files, leaving some lifecycle gaps.
Maintenance
ActivitySlowing
ResponsivenessNo issues