Skip to main content
Glama
Sign In
seedance-mcp

seedance-mcp

by atharva3vedi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to seedance-mcp

No user-submitted related servers found.

    Related Servers

    • google-flow-mcp

      RohaanA
      A
      license
      C
      quality
      C
      maintenance
      Enables Claude, Cursor, or any MCP client to create consistent AI characters, generate Veo 3.1 and Omni videos, edit clips, build scenes, export MP4s, and chat with Google Flow's creative agent. Automates AI video production workflows such as reels, storyboards, and multi-shot stories through natural language, with credit guardrails and dry-run pricing.
      23
      12
      MIT

    • GoogleFlow_MCP

      marvicqui
      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

    • emaki

      hanshs474
      A
      license
      A
      quality
      B
      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
      53 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target distinct actions (generate, cancel, estimate, check), and the spend trio of estimate_cost/spend_status/preapprove_spend is clearly differentiated by description. The only mild overlap is video_task (single status) versus list_video_tasks (batch listing), which descriptions resolve adequately.

    Naming Consistency4/5

    Snake_case is used throughout and most names follow a verb_noun pattern (generate_video, cancel_video_task, estimate_cost, check_setup). Minor deviations are the noun-phrase names video_task and spend_status, which read less like actions than their peers.

    Tool Count5/5

    Nine tools is well-scoped for a media-generation service with spend controls, covering generation, task lifecycle, and cost management without redundancy. Each tool earns its place.

    Completeness4/5

    The surface covers generation (video/image), task lifecycle (status, list, cancel), and the full cost-approval loop, which is strong coverage. A minor gap is the asymmetry where video tasks have status/list/cancel lifecycle but images have no equivalent task-status tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources