OmniFlow MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OF_OUT | No | Output directory for generated clips. Defaults to 'omniflow-out' in the current working directory. | omniflow-out |
| OF_HOST | No | Host address for the local bridge. Defaults to 127.0.0.1 (localhost only). Set to 0.0.0.0 to allow connections from other machines. | 127.0.0.1 |
| OF_PORT | No | Port for the local bridge. Defaults to 8787. | 8787 |
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 | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| flow_statusA | Bridge and extension state: whether the OmniFlow extension is connected, whether a Google Flow project tab is open, what is queued — plus |
| flow_generateA | Queue a generation in the live Google Flow through the extension. Returns jobId immediately WITHOUT waiting for the clips — wait with flow_wait. File paths (frames/characters) are absolute; the bridge reads them. Paths on another machine are unreachable: ask the user to copy files to the machine where the bridge runs. |
| flow_editA | Edit an ALREADY FINISHED video in the Omni 1.1 editor (video-to-video): the extension opens the last clip in Flow, applies the described change and downloads the result. Requires "Trusted input" enabled in the extension. Wait for the result with flow_wait. |
| flow_waitA | Wait for a job to finish and return the file paths. Polls the bridge every 5 s up to timeoutSec. |
| flow_cancelA | Remove everything that has not started generating yet. Clips already in progress are not interrupted. |
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 5 tools
Each tool has a clearly distinct role: status checks connection/state, generate queues new work, edit modifies finished videos, wait polls for completion, and cancel removes queued work. Even though generate and edit both ultimately produce jobs, their descriptions make the different input contexts unambiguous.
All tools follow the same flow_ prefix with a single descriptive verb or noun suffix: status, generate, edit, wait, cancel. This creates a predictable and easy-to-navigate naming scheme.
Five tools is a tight, well-scoped set for an OmniFlow generation/editing bridge. Each tool maps to a necessary stage in the workflow without redundant or filler tools.
The core lifecycle is covered: check status, generate, edit, wait, and cancel queued jobs. Minor gaps exist such as no explicit way to cancel an in-progress job or list finished job history, but these are workable for the primary use case.