dreamina-mcp
Related Servers
Alternatives to dreamina-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables Claude to drive Google Flow end-to-end: batch video generation on Veo 3 / Omni 1.1, scene chaining, keyframe transitions, video-to-video edits, and automatic downloads, all through a local bridge with the OmniFlow Chrome extension.518 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude to control a full-stack video editor by issuing commands to add clips, text, animations, and render MP4 videos, with changes reflected in real-time in the browser UI.-
- AlicenseAqualityDmaintenanceEnables Claude Code to generate, edit, blend, and create variations of images using BytePlus SeeDream AI models, with streaming and Firebase sync.6MIT
- AlicenseBqualityBmaintenanceEnables natural language control of DaVinci Resolve, allowing Claude to browse projects, edit timelines, apply color grades, render exports, and perform AI-powered frame analysis via Moondream.7712MIT
- AlicenseNot gradedqualityDmaintenanceEnables video processing operations (speed adjustment, keyframe optimization, concatenation, and file management) using FFmpeg via Claude Desktop.83 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables automated sound design spotting from Claude Code: analyze video, generate cue sheets, search or generate SFX, and export DAW-synchronized stems.8 npmMIT
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.