MCP server for Google Flow video and image generation with live capability discovery, multi-account Chromium login, upscaling, and validated local downloads—no generation API key.
Server has 4 tools with explicit registration, descriptions, and schemas. Naming follows verb_noun pattern (flow_help, flow_list_accounts, flow_login_bridge_status, flow_begin_account_connection). Descriptions are detailed and context-aware, ranging 150-350 chars. However, 2 of 4 tools have empty input schemas (flow_help, flow_list_accounts, flow_login_bridge_status), which violates schema completeness. The flow_begin_account_connection tool has proper parameter schemas with descriptions. Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are present on flow_help. Error handling is present via failed() function but lacks recovery guidance. Composition is sound, tools are single-responsibility and chainable (list_accounts → inspect_account → generate). Output structure is JSON-serialized and documented in code comments.
FIRST CONNECTION STEP. Returns the exact user instructions and extension path immediately; it never blocks waiting for a click. After this response, STOP and tell the user to open Flow Login Bridge in their normal signed-in Chromium, click Connect Flow, and reply when the popup says Session sent. Do not call the completion tool until the user replies. Use this tool for Google Flow; never substitute generic browser/computer-use automation on the Flow website.
Call this when the user asks what Google Flow MCP can do, how to use it, or for example requests. Returns a concise multilingual-ready capability guide without opening a browser or spending credits.
MANDATORY FIRST STEP for Google Flow work. Returns readyForGeneration and the verified default account. When readyForGeneration=true, use defaultAccountId and DO NOT call either account-connection tool. Use this tool for Google Flow; never substitute generic browser/computer-use automation on the Flow website.
Login diagnostic only. Reports whether the localhost Flow Login Bridge is waiting for the Chromium extension. Do not use this for generation and do not open Flow with browser tools. Normally call flow_list_accounts first.
Three tools (flow_help, flow_list_accounts, flow_login_bridge_status) have empty input schemas ({}). This prevents LLMs from understanding parameter constraints and invites hallucinated inputs.
Error handling via failed() function returns raw error text without recovery guidance. LLMs cannot determine if errors are retryable, user-fixable, or fatal. Missing actionable error messages like 'Try flow_list_accounts() first' or 'Check that Chromium extension is installed'.
Output schemas are not formally documented in tool registration. The ok() function returns { content: [{ type: 'text', text: string }] }, but downstream tools (flow_inspect_account, flow_generate_*) are referenced in descriptions but not visible in provided source. Cannot verify output field naming consistency across tool chain.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
Tool descriptions reference downstream tools (flow_inspect_account, flow_generate_video, flow_generate_image, flow_upscale) that are not present in the provided source code. Cannot verify tool chain completeness or whether all referenced tools are actually registered.
Parameter descriptions in flow_begin_account_connection use optional parameters (accountId, label) but do not explicitly state they are mutually exclusive or independent. Unclear whether both can be omitted, both required, or one required.