No user-submitted related servers found.
Scored across 45 tools
The set is dominated by near-duplicate generations: get_video_status is explicitly an alias for get_video_job, flow_browser_generate_video and flow_browser_autopilot are aliases for generate_video, and generate_video/regenerate_video/refine_video plus list_flows/create_flow/trigger_flow form clusters an agent can easily confuse. The 'legacy bridge workflow' vs 'Google Flow' distinction is only stated in descriptions and is easy to miss when selecting a tool, and flow_browser_action (create/edit/run/export) overlaps with nearly every generation tool.
All names are snake_case, but the ordering convention is split between noun_verb (calendar_delete_event, drive_create_folder, sheets_read) and verb_noun (list_flows, generate_video, download_flow_video). Worse, the 'flow_' prefix is overloaded to mean both legacy bridge workflows (create_flow, trigger_flow) and browser automation (flow_screenshot), so names actively mislead about what family a tool belongs to.
At 45 tools this is far past a comfortable surface, and a meaningful fraction are compatibility aliases (get_video_status, flow_browser_generate_video, flow_browser_autopilot) or legacy bridge tools that could be a separate server. The Google Workspace tools (Gmail, Drive, Sheets, Docs, Calendar) also inflate the set well beyond the server's stated Flow purpose.
The Flow video lifecycle is genuinely deep — generate, status, list, cancel, refine, regenerate, recover, health, plus capability discovery — so the core domain is well covered. However the Workspace half is partial (no Gmail delete/labels/thread listing, no Drive move/rename, no Docs update/delete), leaving scattered gaps that force workarounds.