Skip to main content
Glama
Sign In
GoogleFlow_MCP

GoogleFlow_MCP

by marvicqui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to GoogleFlow_MCP

No user-submitted related servers found.

    Related Servers

    • Codex Image Control MCP Server

      Mahiruxia
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local image generation control and storyboard planning within Codex, supporting continuous image editing, formal image writing, video prompt management, and user-configured video connectors.
      Apache 2.0

    • Ezkielyna Image MCP

      EzkielynaGroup
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants such as Claude Desktop, Claude Code, Cursor, and OpenCode to generate new images from text prompts and edit or combine local image files, saving the results to a local folder. Supports model listing with per-image pricing, reference images up to 4, and safe per-session caps on paid calls.
      518 npm
      MIT

    • Void Media MCP

      SweetRetry
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to generate images, video, and audio through ByteDance Ark and Tu-zi, with OAuth-protected tools for browsing models, confirming quoted costs, tracking tasks, previewing outputs, and auditing spend. Every generation is logged, stored in R2, and priced against catalog list rates.
      402 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: video generation, video extension, image generation, operation status, asset listing, and model listing. The only conceptual proximity is between flow_generate_video and flow_extend_video, but their descriptions clearly separate creation from continuation.

    Naming Consistency5/5

    All tools follow a consistent flow_verb_noun pattern in snake_case: flow_generate_video, flow_extend_video, flow_check_operation, flow_generate_image, flow_list_assets, flow_list_models. There are no mixed conventions or vague names.

    Tool Count5/5

    Six tools are well-scoped for a media-generation server, covering generation, extension, status checking, image creation, and listing assets/models. Each tool earns its place without bloating the surface.

    Completeness4/5

    The surface covers the core Flow workflow: generate video/images, extend videos, check pending renders, and list assets/models. Minor lifecycle gaps exist, such as canceling operations or deleting assets, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources