OpenCode Integration with Seedance MCP

📘 Overview：OpenCode MCP Overview →

Seedance performs particularly well in "short videos / vertical materials / action performances," providing complete pieces with audio in one go, making it very suitable for direct use as social media content. After connecting the Seedance MCP Server in OpenCode, you can generate animated videos directly from a single sentence of requirements, eliminating the intermediate steps of editing and voiceover.

Seedance MCP is suitable for creating Reels / Douyin / Xiaohongshu short videos, product demo animations, technical sharing opening clips, and other "short and impactful" video scenarios.

Obtain API Token

Before using the Seedance MCP Server, you need to prepare an Ace Data Cloud API Token. OpenCode and Claude Code share the same set of Tokens, and the acquisition process is the same:

  1. Open the Ace Data Cloud Console - Application List to obtain your API Token for backup.
  2. If you are not logged in or registered, you will be automatically redirected to the login page; after logging in or registering, you will be returned to the current page.
  3. The first application will have a free quota available, allowing you to experience Seedance MCP services for free.

One Token can be used for all 11 MCP Servers provided by AceData Cloud, without needing to apply separately for Seedance. The documentation and screenshots suggest displaying only in a desensitized format, such as 3b78cc40dd3b43db806a4300...., and not posting the full Token in public repositories, issues, screenshots, or chat logs.

Want to use Claude Desktop / Claude.ai web version for direct OAuth one-click authorization? Please see the Claude.ai / Desktop tutorial for Seedance MCP.

Configure OpenCode

OpenCode describes all MCP Servers in a single opencode.json file, which can be placed in two locations; choose one based on the "scope of application" below. The field structure in both locations is identical, with the only difference being priority.

It is strongly recommended to first write the Token to an environment variable:

export ACEDATACLOUD_API_KEY="replace with your real Token"

Then reference it in opencode.json using the {env:ACEDATACLOUD_API_KEY} placeholder to avoid writing the real Token into the file.

Global: Shared by all projects

File location: ~/.config/opencode/opencode.json, suitable for "my own machine, configured once, usable by all projects."

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "seedance": {
      "type": "remote",
      "url": "https://seedance.mcp.acedata.cloud/mcp",
      "enabled": true,
      "oauth": false,
      "headers": { "Authorization": "Bearer {env:ACEDATACLOUD_API_KEY}" }
    }
  }
}

⚠️ "oauth": false cannot be omitted. AceData's MCP Server uses Bearer Token authentication and does not go through the OAuth process; OpenCode will automatically redirect 401 as an OAuth challenge, resulting in opencode mcp list showing SSE error: Non-200 status code (401). Explicitly declaring "oauth": false allows OpenCode to call directly with Authorization: Bearer ..., and opencode mcp debug seedance will also echo OAuth explicitly disabled, indicating it is effective.

Project-level: Effective only for the current project

File location: opencode.json in the current project root directory, which will override the global configuration. Suitable for team sharing, single repository customization, or temporarily enabling a specific MCP in a project.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "seedance": {
      "type": "remote",
      "url": "https://seedance.mcp.acedata.cloud/mcp",
      "enabled": true,
      "oauth": false,
      "headers": { "Authorization": "Bearer {env:ACEDATACLOUD_API_KEY}" }
    }
  }
}

If the project-level opencode.json will be committed to Git, please ensure to use the {env:ACEDATACLOUD_API_KEY} placeholder instead of the real Token to avoid leakage.

💡 If the .env in Shell is not explicitly exported, you need to use set -a && source .env && set +a to pass the variables to the OpenCode process; otherwise, opencode debug config will show "Authorization": "Bearer " (placeholder not resolved).

Actual Running Results

Below is the desensitized output after actual execution in an isolated temporary directory using OpenCode 1.15.13. The command uses the real AceData Cloud Token, and the Token in the output has been replaced with 357265014ad145fc8ab2...., and the temporary configuration has been deleted.

$ opencode --version
1.15.13

$ opencode mcp list

┌  MCP Servers
│
●  ✓ seedance connected
│      https://seedance.mcp.acedata.cloud/mcp
│
└  1 server(s)

Seeing ✓ seedance connected indicates that the Seedance MCP has been successfully integrated. If it shows ✗ or unauthorized, please check whether ACEDATACLOUD_API_KEY is set, whether the Token is copied completely, and whether the Authorization prefix is Bearer (pay attention to case and spaces).

To debug the connection details of a specific MCP:

opencode mcp debug seedance

After a successful handshake, OpenCode's INFO log will output service=mcp key=seedance transport=StreamableHTTP connected and service=mcp key=seedance toolCount=7 (7 tools tested), indicating that the Seedance MCP is ready to be called by the model.

🤖 Model selection testing suggestions: To truly allow the model to actively call the Seedance MCP in OpenCode, please prioritize using OpenAI series models (such as acedatacloud/gpt-5-mini, acedatacloud/gpt-5). When the Claude series models on AceData are exposed through the OpenAI compatible interface, tool calls often return Improperly formed request (tested: acedatacloud/claude-haiku-4-5-20251001, acedatacloud/claude-sonnet-4-6 reported this error when mounting multiple MCPs). Claude models can be used normally when only doing dialogue without calling tools.

Typical Scenarios

After configuration is complete, you can directly call using natural language in the OpenCode session without switching to /mcp:

Text to generate short video

Generate a vertical short video: a girl turns under a cherry blossom tree, slow motion, beautiful light and shadow

Image to video

Use this image as a cover, generate a video with the camera slowly zooming in

Generate video intro

Generate a 3-second video intro: a glowing code symbol </> transitions from blurry to clear, with particle effects in the background, in a tech blue tone

Tool List

The table below lists the main tools (The Seedance MCP Server has exposed a total of 7 tools, which can be obtained through curl -X POST https://seedance.mcp.acedata.cloud/mcp -H 'Authorization: Bearer <token>' -H 'Accept: application/json' -H 'Content-Type: application/json' --data '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' for a complete list):

Tool Description
seedance_generate_video Generate video from text
seedance_generate_video_from_image Generate video from image