Google Flow MCP
by UmutKDev
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP port. | 8080 |
| FLOW_COOKIES | No | Cookies content as text: base64 (recommended), JSON, or cookies.txt. Use this for Obot. | |
| FLOW_HEADLESS | No | 1 uses headless Chrome (may be rejected by reCAPTCHA). | 0 |
| FLOW_MCP_PATH | No | HTTP path. | /mcp |
| FLOW_SYNC_WAIT | No | Time a tool waits before returning a job ID (seconds). | 40 |
| FLOW_INPUT_DIRS | No | Additional directories from which flow_upload_image may read files. | |
| FLOW_OUTPUT_DIR | No | Directory for upscaled files, budget ledger, and state. | /tmp/google-flow-mcp |
| FLOW_PROJECT_ID | No | Default Flow project. | |
| FLOW_JOB_TIMEOUT | No | Maximum wait for a video to become ready (seconds). | 900 |
| FLOW_PROFILE_DIR | No | Persistent Chrome profile directory (Docker volume). If provided, cookies are not needed. | |
| FLOW_COOKIES_FILE | No | Path to the exported cookies file (Docker volume, Kubernetes Secret). | |
| FLOW_BROWSER_PROXY | No | Proxy for Chrome (e.g. http://host:port). | |
| FLOW_MCP_TRANSPORT | No | Transport to use; can be stdio or streamable-http. | streamable-http |
| FLOW_BUDGET_CREDITS | No | Maximum credits that can be spent on video. 0 disables video. | 200 |
| FLOW_MCP_AUTH_TOKEN | No | If set, every request must include Authorization: Bearer <token>. | |
| FLOW_EXPECTED_ACCOUNT | No | Expected Google email address. | |
| FLOW_CONFIRM_THRESHOLD | No | Requests above this estimated cost require confirm=true. | 1 |
| FLOW_DEFAULT_IMAGE_MODEL | No | Default image model. | NANO_BANANA_PRO |
| FLOW_MIN_SUBMIT_INTERVAL | No | Minimum time between two paid requests (seconds). | 4 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues