OpenCode Integration with Seedream MCP

📘 Overview：OpenCode MCP Overview →

Seedream's understanding of Chinese prompts and its performance in product images and poster scenarios has always been stable, especially in "editing existing images based on descriptions," which can almost be directly handed over to design colleagues. After connecting the Seedream MCP Server in OpenCode, you can directly describe the image you want in Chinese, or let the AI modify the existing images you paste in.

Seedream MCP is suitable for e-commerce product images, event posters, social media graphics, as well as "secondary editing" scenarios like modifying text on posters and adjusting visual elements.

Obtain API Token

Before using the Seedream 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 automatically returned to the current page.
  3. The first application will have a free quota available, allowing you to experience the Seedream MCP service for free.

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

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

Configure OpenCode

OpenCode describes all MCP Servers in a single opencode.json file, which can be placed in two locations; choose one according to the "scope of application" below. The field structure in both locations is exactly the same, 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": {
    "seedream": {
      "type": "remote",
      "url": "https://seedream.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, causing opencode mcp list to show SSE error: Non-200 status code (401). Explicitly declaring "oauth": false allows OpenCode to call directly with Authorization: Bearer ..., and opencode mcp debug seedream 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 certain project.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "seedream": {
      "type": "remote",
      "url": "https://seedream.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 in 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
│
●  ✓ seedream connected
│      https://seedream.mcp.acedata.cloud/mcp
│
└  1 server(s)

Seeing ✓ seedream connected indicates that the Seedream 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 seedream

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

🤖 Model selection testing suggestions: To truly allow the model to actively call the Seedream 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:

Generate an image with a single Chinese sentence

Generate a Spring Festival promotional poster: red background, golden fortune character, milk tea shop products, square

Edit the text of an existing image

Change "v1.0" on this poster to "v2.0", keeping everything else the same

Generate a product image with a white background

Generate a product image with a white background: minimalist style table lamp, viewed from a 45-degree angle

Tool List

The table below lists the main tools (Seedream MCP Server has exposed a total of 6 tools, which can be obtained through curl -X POST https://seedream.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
seedream_generate_image Generate images from text
seedream_edit_image Edit existing images (change text, change elements)