Connect with MCP
Remote server
URL: https://seedance-2.app/api/mcp
The server uses Streamable HTTP with JSON responses and no persistent transport session. It negotiates supported MCP protocol versions including 2025-06-18. Use a client that supports a remote MCP URL and OAuth 2.1, or a client that can send an API key as a Bearer header.
OAuth connection
- Add the remote server URL in your client's MCP connection settings.
- Choose OAuth or automatic authentication.
- Sign in to Seedance and inspect the application's name, redirect destination and requested permissions.
- Explicitly allow access. The client returns to its registered redirect URI and exchanges a single-use S256 PKCE code.
- Start with
list_modelsorget_credit_balance.
Discovery metadata is available at /.well-known/oauth-protected-resource/api/mcp and /.well-known/oauth-authorization-server. Public clients can register at /api/oauth/register. Access tokens last one hour; refresh tokens rotate. Revocation invalidates the token family. An OAuth grant is bound to this MCP resource and does not become an unrestricted browser session.
Tools
| Tool | Permission | Cost behavior |
|---|---|---|
list_models | models:read | Reads model contracts |
quote_generation | models:read | Validates inputs; no reservation |
create_generation | generations:create | Requires an explicit credit cap and idempotency key; uses your account credits |
get_generation | tasks:read | Reads/refreshes your task only |
get_credit_balance | credits:read | Reads site credits |
Tell the client what you want to create. Have it obtain a quote before generation and use that quote as maxCostCredits. It should preserve the idempotency key for a retry and poll the accepted task rather than create another copy.
API key clients
Clients without OAuth can send Authorization: Bearer YOUR_API_KEY. Create the key in Settings → API Keys. Keys grant access to the owner's generation account and credit balance; revoke unused keys from the same settings page.