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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DanikVR/omniflow-veo-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server