Skip to main content
Glama

Related Servers

Alternatives to dreamina-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables any MCP client such as Claude, Cursor, Cline or Gemini CLI to generate Seedance 2.5, Seedance 2.0, MiniMax H3 and Veo 3.1 videos and still images from text or a reference image using your own account. It also exposes run-status polling and remaining-credit checks, with configurable duration, resolution, aspect ratio and audio.
      4
      52 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code and Codex to generate, extend, and manage Veo videos and Nano Banana images from natural-language prompts, with local output storage and asset tracking. It also supports image-to-video consistency workflows, model discovery, and a storyboard prompt for step-by-step rendering.
      6
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code to drive Google Flow through a shared, visible Chrome window controlled over CDP, exposing 26 tools for creating projects, handling login, preparing and submitting generations, and downloading or saving generated media.
      130 npm
      MIT

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues