home / mcp / seedream image mcp server

Seedream Image MCP Server

🚀 PixelMCP | 为你的 Cursor、Claude Code 等集成AI绘画能力，让AI生成的页面不再单调！

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "wearzdk-seedream-image-mcp": {
      "command": "npx",
      "args": [
        "seedream-image-mcp",
        "--ark-key=YOUR_API_KEY"
      ]
    }
  }
}

You can generate high‑quality images using the SeeDream Image MCP tool, built on Volcano Engine’s SeeDream model. It exposes an MCP interface so you can drive image generation from clients like Cursor or Claude Desktop, while handling API authentication and prompt generation for you.

How to use

Set up and run the MCP server locally or connect via a compatible MCP client. The key entry point is a simple command you run in your terminal, which forwards your request to the SeeDream image service and returns generated images.

How to install

Prerequisites you need on your machine before you begin:

Node-compatible runtime that supports Bun is recommended for this workflow.
A Volcano Engine API Key is required to authenticate requests. You obtain it from the Volcano Engine Control Center.

Install dependencies and run locally using Bun. Execute the following commands in order.

bun install

bun run src/index.ts --ark-key=YOUR_API_KEY

Configuration to connect clients

If you want to connect MCP clients like Cursor or Claude Desktop, configure the MCP server entry with the following JSON snippet. This setup uses the CLI to run the MCP tool and passes your API key as a parameter.

{
  "mcpServers": {
    "seedream-image": {
      "command": "npx",
      "args": ["seedream-image-mcp", "--ark-key=YOUR_API_KEY"]
    }
  }
}

Usage with AI agents

In an AI Agent tool, you can prompt the agent to request an image for a page. The agent will automatically invoke the MCP tool to generate the image according to the request.

Notes and best practices

Image links generated by the SeeDream MCP flow come from Volcano Engine’s raw API. These links typically expire after 24 hours. If you need to keep images long term, download them locally as soon as they are generated.

Two usage modes

Mode 1 — Local run (requires your own API key): You manage the API key yourself and run the MCP server on your machine. The image links expire after 24 hours, so you should download any images you want to keep.

Mode 2 — Cloud version (no API key required): The cloud version stores images on a CDN, supports WebP compression, background removal, and high-concurrency generation. It offers a certain amount of free usage and pricing scales with volume.

开发与许可证

This server is released under the MIT license.