F
licenseNot graded
qualityD
maintenanceEnables generative AI media tasks like image generation, editing, icon creation, and story generation using Google Gemini API through MCP.
-
google-flow-mcp
by Reasonofmoon
Related Servers
Alternatives to google-flow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables any MCP client to generate, edit, and upscale images, video, audio, and films across 140+ AI models, with tools for ads, characters, storyboards, and reusable workflows.429 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to produce motion videos from a brief, using frontier models for creative direction and cheaper models/tools for rendering and finishing.2MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables image generation, editing, and blending using Gemini 2.5 Flash capabilities, plus text generation for AI-powered creative workflows through MCP tools.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to generate and edit images from natural-language requests, automatically enriching prompts with details like composition, lighting, and camera angle. It supports quality presets and multiple providers, including Gemini, OpenAI, and BytePlus Seedream.1,781 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered image generation and editing using Gemini and Imagen models, supporting text-to-image, image editing, and multi-image composition through MCP tools.MIT
TDQS
A3.7/5.0
Scored across 21 tools
Disambiguation4/5
Most tools target a distinct resource+action: image generate/edit/reference, video generate/extend/edit, storyboard plan/keyframe/render, and assembly. A few pairs share inputs and could be momentarily confused (flow_edit_video vs flow_extend_video both take video_path/previous_interaction_id; flow_generate_video vs flow_image_to_video), but the descriptions draw clear boundaries (edit changes content, extend continues the scene).
Naming Consistency3/5
All names are snake_case with a uniform flow_ prefix, which is good, but verb/noun ordering is mixed: verb_noun in flow_generate_image, flow_edit_video, flow_list_presets, yet noun_verb in flow_ingredient_save, flow_storyboard_plan, flow_shot_update, plus bare nouns/verbs like flow_project, flow_board, flow_assemble. Readable, but not a predictable single pattern.
Tool Count4/5
21 tools is above the ideal 3-15 band, but the surface maps to a genuine multi-stage studio workflow (project setup, ingredients, storyboard, keyframes, renders, audio, assembly, review), so almost every tool earns its place. Minor redundancy exists between image-to-video and the generate/extend pair.
Completeness4/5
Covers the full lifecycle: project creation, reusable ingredients, storyboard authoring, keyframe preview, video rendering, music/narration, final assembly, cost estimation, usage tracking, and visual review. Gaps are minor: no explicit ingredient or take deletion, no project listing/selection beyond the active project, and no subtitle/caption tooling.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues