Seedance MCP: make Seedance 2.5 clips from Claude Code

To use Seedance over MCP, connect a remote server that runs it. On Sume's, generate_video takes four Seedance ids, with 30-second clips on 2.5.

5 min readSume
All posts

To use Seedance from Claude Code or Cursor, connect a remote MCP server that runs the Seedance video models: Higgsfield, Runway and Sume each list Seedance 2.5 for MCP clients. On Sume's hosted server, generate_video takes seedance-2.5, seedance-2, seedance-2-fast or seedance-2-mini, and seedance-2.5 makes clips of 4 to 30 seconds.

Sume's side comes from its MCP overview, MCP quickstart and Video generation docs, the API reference and current catalog code; the other servers come from their own pages. All were read on 2026-09-28. The basics page says hosted MCP still works but is not the primary path today; from a backend, Seedance 2.5 API shows the POST /v1/videos call.

Which MCP servers run Seedance?

Three remote servers read for this post name Seedance, and they differ in which Seedance versions they expose. Each bills its own balance:

Seedance versions per server, from each one's own pages (1, 2, 3) and Sume's MCP overview and Video generation, read 2026-09-28. Alphabetical.
ServerEndpointSeedance versionsBilled as
Higgsfieldhttps://mcp.higgsfield.ai/mcpSeedance 2.5, Seedance 2.0Plan credits, by model and resolution
Runwayhttps://mcp.runwayml.com/mcpSeedance 2.5, based on your Runway planPlan credits
Sumehttps://mcp.sume.com/mcpseedance-2.5, seedance-2, seedance-2-fast, seedance-2-miniWorkspace USD balance, per 1,000 video tokens

How do I add Seedance to Claude Code?

For Sume, run claude mcp add --transport http sume https://mcp.sume.com/mcp, then claude mcp login sume, and turn Write on at consent so paid tools can run; Sume MCP server for Claude Code, Cursor and Codex covers scopes and the other clients.

Then ask for a Seedance id. A 20-second vertical teaser, previewed first with dry_run, looks like this:

{
  "idempotency_key": "seedance-launch-teaser-001",
  "dry_run": true,
  "payload": {
    "model": "seedance-2.5",
    "prompt": "a paper boat drifting down a rain gutter, low angle, soft rain",
    "duration": 20,
    "resolution": "720p",
    "aspect_ratio": "9:16"
  }
}

Which Seedance id should I name?

Without payload.model, generate_video routes to sume/auto, so name the id. seedance-2.5 is the one that runs past 15 seconds, at 4 to 30 seconds and 480p, 720p or 1080p; the other three top out at 15 seconds, and seedance-2 also offers 1080p. Seedance 2.5 API lists each id's inputs and limits, and Seedance 2.0 Fast vs Mini compares those two. Frame and reference files must be reachable over public HTTPS; the other MCP-side rules are the same as in Kling MCP for Claude Code.

How long does a Seedance job take over MCP?

The tool answers with a job id, not a clip. The docs say video generation typically takes 30 seconds to several minutes. One jobs_wait call holds at most 55 seconds, so the agent waits in slices: on wait_slice_expired, call jobs_wait again with the same id and never resubmit the paid create; then read jobs_result. MCP tool call timeouts on long video jobs covers client timeouts.

How much does Seedance cost over MCP?

On Sume, video is billed from the workspace USD balance, reserved on submit at provider list × 1.25, plus a 5.5% agent fee by default. In current catalog code, every Seedance id is priced per 1,000 video tokens rather than per clip or per second, so run the call with dry_run: true to see the amount first, and send max_spend_usd to cap it.

Sources

Related posts

More in Models

All Models posts

Written by Sume