Google Flow MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOW_URL | No | Target web application URL | https://flow.google.com |
| BROWSER_PATH | No | Explicit path to a browser binary | Auto-detected |
| FLOW_DEBUG_PORT | No | Remote debugging port | 9222 |
| FLOW_PROFILE_DIR | No | Session and cookie persistence directory | ~/.google-flow-mcp/profile |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flow_statusB | Checks local browser connection, background status, and local Google Flow login state. |
| flow_launch_browserC | Controls local browser execution mode (headless background vs headed window for 1-time login). |
| flow_open_tabB | Navigates to or focuses Google Flow in your local browser. |
| flow_inspect_canvasB | Inspects active Google Flow workspace: returns prompt inputs, action buttons, and canvas nodes. |
| flow_execute_promptC | Injects a creative prompt into Google Flow and triggers generation in your personal workspace. |
| flow_clickB | Clicks an element in the page by CSS selector, text, or aria-label. |
| flow_screenshotA | Captures a screenshot of the active Google Flow workspace in your local background browser. |
| flow_eval_jsC | Runs custom JavaScript in the active page context on your local browser. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: status, browser launch mode, tab navigation, canvas inspection, prompt execution, clicking, screenshot, and JS eval. The only mild overlap is flow_launch_browser vs flow_open_tab and the low-level flow_click vs flow_eval_js, but the descriptions distinguish them adequately.
All tools use a consistent flow_ prefix with snake_case, and most follow a verb_noun shape (launch_browser, open_tab, inspect_canvas, execute_prompt). flow_status is a minor noun-only deviation, but overall the convention is predictable.
Eight tools is well-scoped for a browser-automation server, covering setup, navigation, inspection, action, and debugging without redundancy. Each tool earns its place.
The surface covers the full browser-automation lifecycle: connection/status, launch mode, navigation, inspection, prompt execution, clicking, screenshots, and arbitrary JS. Minor gaps exist (no explicit text/typing, scroll, or wait tools), but flow_eval_js and flow_click let agents work around them.