Skip to main content
Glama

Related Servers

Alternatives to Google Flow MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to programmatically generate images and videos through the authenticated Google Flow web interface via a direct Chrome DevTools Protocol connection, exposing tools for media generation, project management, status checks, and asset downloads without requiring official API keys.
      7
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants such as Claude Code, Codex, and Cursor to generate images and videos through Google Flow using a local, already signed-in Chrome session. It runs as a local MCP endpoint so assistants can submit generation jobs, manage them, and receive results using your own Flow subscription credits.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to drive a Google Flow web workspace through local login-session reuse: inspecting the account's actual models and parameters, submitting image and video generation jobs, tracking each job by persistent ID, and downloading the matching media to a specified local path with file and parameter records. Supports repeatable, multi-shot video production workflows where tracked assets are handed off to editing tools like FFmpeg.
      11
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Drives Google Flow from an agent or the terminal: Veo text-to-video, image-to-video and clip extension, plus Imagen image generation. Runs locally against your own Google account with Flow access; video generation bills that account's credits.
      16
      1,013 PyPI
      251
      MIT

    TDQS

    B3.4/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target distinct operations, but there is some overlap between flow_status and flow_queue_status, and flow_use_tool potentially overlaps with specific tools like flow_use_grid_architect or flow_open_tools_gallery. However, the descriptions generally clarify the intended boundaries.

    Naming Consistency5/5

    All tool names follow a consistent flow_ prefix with snake_case verb/noun structure (e.g., flow_connect, flow_generate_image, flow_create_character). There are no mixed conventions or confusing naming patterns.

    Tool Count4/5

    At 17 tools, the set is slightly heavy but still reasonable for a browser automation server covering connection, UI discovery, generation, characters, scenes, and queue monitoring. Most tools appear to earn their place, though a few could potentially be consolidated.

    Completeness3/5

    Core workflows like connection, generation, and character/scene creation are covered, but there are notable gaps such as no update/delete operations for characters or scenes, no explicit scene listing, and no job cancellation or cleanup tool beyond disconnection. These omissions could limit full lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues