dreamina-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OF_OUT | No | Directory where generated clips are saved. Defaults to 'seedflow-out/' in the current working directory, falling back to ~/seedflow-out if not writable. | seedflow-out |
| OF_HOST | No | Host/interface the local bridge listens on. Defaults to 127.0.0.1. 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 8788. | 8788 |
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 |
|---|---|
| dream_statusA | Bridge and extension state: whether the SeedFlow extension is connected, whether a Dreamina video-generator tab is open, what is queued — plus |
| dream_generateA | Queue a Seedance 2.5 generation in the live Dreamina through the extension. Returns jobId immediately WITHOUT waiting for the clips — wait with dream_wait. File paths (refs/frames) are absolute and are read by the bridge. |
| dream_editA | Edit an ALREADY FINISHED video in Dreamina (video-to-video Seedance 2.5) from a change description. Opens the clip detail view and triggers the Dreamina action (Edit video, Extend, Creative upscale, Interpolate, Generate soundtrack, Regenerate). Wait for the result with dream_wait. |
| dream_waitA | Wait for a job to finish and return the file paths. Polls the bridge until the timeout; returns the intermediate picture if it is not done yet — that is not an error, just call again. |
| dream_cancelA | Remove everything that has not started generating yet. Running clips 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 maps to a distinct lifecycle stage: status (pre-flight check), generate (new job), edit (modify existing video), wait (poll result), cancel (drop queued jobs). Generate vs edit is clearly delineated by 'new' vs 'already finished video', so an agent can select correctly.
All five tools use the same dream_verb snake_case pattern (dream_status, dream_generate, dream_edit, dream_wait, dream_cancel). Fully predictable and consistent.
Five tools is well-scoped for a generation bridge: the workflow of check-state, submit, edit, wait, and cancel is compact with no redundant entries. Every tool earns its place.
The core async lifecycle (status → generate/edit → wait → cancel) is fully covered, including polling semantics. Minor gaps: no way to list/history past jobs or query an arbitrary job by id outside of wait, but these are workable arounds rather than dead ends.