Seedance in Claude: How to Run Seedance 2.5 From a Chat

Seedance in Claude means you ask Claude for a video and get a real Seedance 2.5 clip back. This guide covers the setup, one clip we made and the credits it cost. Claude has no video model of its own, so it calls one over MCP. We used Wireflow, the node-based AI canvas we build, whose connector lets Claude run a saved Seedance 2.5 flow and hand back the MP4. On 27 October 2026 our 5-second test clip rendered in 4 minutes 50 seconds and charged 134 credits.

What "Seedance in Claude" actually means

Claude writes text and code but outputs no video frames. Seedance is ByteDance's video model family, and its newest version, Seedance 2.5, makes clips of up to 30 seconds in one pass with sound generated alongside the picture. Putting the two together takes an MCP server that exposes Seedance as a tool Claude can call.

The search results for this phrase mix three different things, and only one of them returns a video:

Route	What Claude does	What you get back
Prompt-writing skill	Writes a Seedance prompt	Text you paste into another tool
Single-model MCP server	Calls one Seedance endpoint	One clip per call
Workflow connector	Runs a saved flow with Seedance as one node	Every node's output, and the same flow over REST

For a wider look at the connector options, see our ranked list of video MCP tools.

How Claude runs Seedance through MCP

The Model Context Protocol (MCP) lets an app publish tools that Claude can call. A video takes minutes, so a video tool starts a job, returns an id and lets Claude check back. Our earlier test of Claude video generation used the same pattern with two other video models.

Our MCP server groups its tools by job. The ones that matter for a Seedance clip:

• list_models shows which models the account can reach and what each costs.
• get_credit_balance returns the balance and plan before anything is spent.
• list_workflows and get_workflow find a flow and the inputs it takes.
• run_workflow starts a run and returns an execution id. It is the only tool that spends credits.
• get_execution returns the status and, once the run finishes, the output URLs.
• create_workflow_from_prompt builds a new flow from a description, behind an opt-in edit permission.

The clip we made: one prompt, Seedance 2.5, 5 seconds

Two working nodes keep the cost and timing down to Seedance alone, in a plain text to video AI setup:

1. Shot Prompt. A text input holding the shot description.
2. Clip (Seedance 2.5). The Seedance 2.5 node at 16:9, 5 seconds, 720p, with audio generation on.

The prompt, word for word:

A barista pours steamed milk into a cup of espresso on a wooden counter in a small sunlit cafe, and a leaf of latte art forms on the surface. Close-up, slow push-in, shallow depth of field, warm morning window light. Sound: the soft hiss of the steam wand, milk pouring into the cup, quiet cafe chatter in the background. No text, no logos.

The loop is the unedited output without sound; click it for the MP4 with audio. Figures come from the run record, and pricing lists the plans behind the credits.

Step	Settings	Finished after	Credits
Shot Prompt	Text input	under 1 s	0
Clip (Seedance 2.5)	5 s, 720p, 16:9, audio on	4 min 50 s	134
Total		about 4 min 53 s	134

The models list prices Seedance 2.5 at 27 credits a second, the rate for a 5-second clip, which quotes 135 credits. The run record charged 134.

What came back

The file is 1280x720 at 24 frames a second, 5.04 seconds long, H.264 video with a stereo AAC sound track made in the same pass. Our Seedance 2.5 review covers the model's specs and how it compares with other video models.

• The motion matched the prompt. The camera pushes in, the milk goes in, and by 4.5 seconds a rosetta pattern sits on the surface.
• One visible glitch. Around 2.5 seconds the pitcher's spout stretches into a long, spoon-like neck that dips into the cup. At full speed it is easy to miss, but a product shot would need a rerun.
• Sound is part of the file. There is no separate audio step, but listen before you ship.

That glitch is the case for keeping a person in the loop: Claude can run a second take or a second model on the same prompt, the idea behind comparing video models side by side.

Set it up and run it from Claude

The connector is a remote MCP server with OAuth sign-in, so there is no API key to paste. It also works in a terminal, the route covered on our AI API with Claude Code integration page.

1. Add the connector. In claude.ai or Claude Desktop, open Customize, then Connectors, click + Add and choose Add custom connector. Give it a name and paste https://www.wireflow.ai/api/mcp as the server URL. In Claude Code, run claude mcp add --transport http wireflow https://www.wireflow.ai/api/mcp.
2. Sign in and approve. Runs are allowed by default; leave the edit permission off unless Claude should build flows.
3. Copy the flow. Open the workflow linked at the end of this guide and duplicate it so it sits in your own account.
4. Ask in plain words. For example: "Run my Seedance 2.5 Clip From Claude flow with this shot: a ceramic mug of tea steaming on a windowsill at dawn, slow push-in. Tell me the credit cost and wait for my yes before you run it."
5. Let Claude poll. It quotes the price, runs run_workflow after your yes, and checks get_execution until it can reply with the MP4 link.

Claude can write the shot too: ask for one shaped like ours (subject, setting, camera move, light, sound, "no text"), read it, then have Claude run it. If the clip needs your own voice rather than generated sound, our guide on how to get your real voice into the clip covers what works.

When to move from Claude to the REST API

Claude is the right front end while a person is choosing: one clip, a tweak, a rerun. It is the wrong place for work nobody watches, since the chat stays busy while a render runs for minutes. Our n8n vs MCP comparison covers that trade-off.

The flow you tested in Claude does not change when you move. Your code sends an API key as a Bearer token, POST /api/v1/workflows/{id}/run starts the run and returns an execution id, and GET /api/v1/workflows/executions/{executionId}/poll returns the status and the output URLs. Our poll record for this run reported creditsUsed: 134, so you can log the cost of each clip next to the file. The request pattern and per-node cost reporting are on the Seedance API page.

	Claude through MCP	REST API
Who starts a run	You, in a chat	Your app, a schedule or a queue
Sign-in	OAuth, no key to paste	API key as a Bearer token
Cost check	Claude reads the price and balance first	Your code reads creditsUsed from the poll
Waiting	The chat waits while Claude polls	A worker polls in the background
Best for	One-off clips and prompt testing	Batches, product features, scheduled runs

API and MCP access are on every plan, and runs use the same credits either way. For request bodies and error handling, follow our step-by-step API guide.

Costs and limits to plan for

Figures are from the live models list and pricing page on 27 October 2026. Other platforms are in our Seedance pricing comparison.

• 27 credits a second. That is the rate for a 5-second clip; shorter clips can cost a bit more per second, and you are charged for the real length. Our 5-second clip charged 134 credits.
• Plans. Starter is $36 a month for 2,660 credits, about 19 Seedance 2.5 clips at 5 seconds and 720p. Professional is $59 a month for 4,370 credits, about 32 clips.
• Length and resolution. The node makes up to 30 seconds in one pass at 480p, 720p or 1080p. At 1080p the file comes back as 10-bit HEVC, which some browsers cannot play.
• Two bills. Claude's tool calls count toward your Claude plan's usage. The generation is charged to the account the connector signs in to.

Try it yourself: Build this workflow in Wireflow. Edit the Shot Prompt and run Clip (Seedance 2.5) for a 5-second, 720p clip with sound. From Claude, one run_workflow call does the same.

FAQ

Can Claude generate videos with Seedance?

Not by itself. Through an MCP connector it can run Seedance 2.5 and return the MP4 link.

Which Seedance versions can Claude use this way?

Any version the flow's video node is set to. Seedance 2.5 is the newest, and Seedance 2.0 is available as a cheaper node, so Claude can run both on one prompt to compare.

How much does one Seedance 2.5 clip cost from Claude?

The models list prices Seedance 2.5 at 27 credits a second, so a 5-second clip quotes 135 credits. Our run charged 134. Claude's own usage counts toward your Claude plan.

Does the clip come with sound?

Yes. Seedance 2.5 generates audio in the same pass as the video, and our clip came back with a stereo track. You can turn audio generation off in the node for a silent clip.

Which Claude apps can run Seedance?

Custom MCP connectors work in claude.ai, Claude Desktop and Claude Code. On managed Team or Enterprise plans, an admin may need to add or allow the connector first, and our guide to connect Claude to video editing shows the same setup for edits.

Do I need an API key to use Seedance in Claude?

No. The connector signs in with OAuth. You only need an API key when your own code calls the flow over REST, for example through a video generation API integration.

Conclusion

Seedance in Claude works today through a connector: Claude writes the shot, quotes the price, runs Seedance 2.5 after your yes and hands back the file. Our 5-second test took under five minutes and 134 credits, with one small glitch worth a rerun. Wireflow keeps that flow the same whether Claude or your code starts it, so the node-based video generation graph you test in a chat is the one your app calls later.