SeeDream MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for HTTP server mode, defaults to 3000 (optional). | |
| TRANSPORT | No | Transport mode: 'stdio' (default) or 'http' (optional). | |
| ARK_API_KEY | Yes | Your BytePlus ModelArk API key, required for image generation. | |
| FIREBASE_SERVICE_ACCOUNT | No | JSON string of Firebase service account credentials (optional). | |
| FIREBASE_SERVICE_ACCOUNT_PATH | No | Path to Firebase service account JSON file for Web App sync (optional). | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Standard GCP credential file path for Firebase (optional). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| seedream_generateA | Generate images from a text description using SeeDream 4.5. ⚠️ CLAUDE.AI USERS: This tool WILL TIMEOUT on Claude.ai (takes 30-60 seconds). Use "seedream_submit" instead with mode="text" for Claude.ai compatibility. This is the primary tool for creating images from scratch. Default: Generates 4 images per prompt using streaming for fast response. Args:
Returns: Generated image URL(s), local file path(s) if downloaded, and performance timing. Prompt Best Practices (per official docs):
Examples:
Tips:
|
| seedream_editA | Edit an existing image based on text instructions using SeeDream 4.5. ⚠️ CLAUDE.AI USERS: This tool WILL TIMEOUT on Claude.ai (takes 20-40 seconds). Use "seedream_submit" instead with mode="image" for Claude.ai compatibility. Use this tool to modify, enhance, or transform an existing image. Supports:
Args:
Returns: Edited image URL, local path if downloaded, and performance timing. Edit Instruction Best Practices (per official docs):
Supported Operations:
Examples:
|
| seedream_blendA | Combine elements from multiple images using SeeDream 4.5. ⚠️ CLAUDE.AI USERS: This tool WILL TIMEOUT on Claude.ai (takes 30-60 seconds). Use "seedream_submit" instead with mode="multi" for Claude.ai compatibility. Use this tool to blend 2-14 reference images together. Perfect for:
Args:
Returns: Blended image URL, local path if downloaded, and performance timing. Prompt Structure (per official docs):
Common Use Cases:
Examples:
Tips:
|
| seedream_variationsA | Generate multiple variations of an image concept using SeeDream 4.5. ⚠️ CLAUDE.AI USERS: This tool WILL TIMEOUT on Claude.ai (takes 30-90 seconds). Use "seedream_submit" instead for Claude.ai compatibility. Use this tool to create 2-15 coherent variations based on a prompt. Great for:
Args:
Returns: Array of variation image URLs, local paths if downloaded, and performance timing. Prompt Best Practices (per official docs):
Examples:
Tips:
|
| seedream_statusA | Check the health and status of the SeeDream MCP server. Use this tool to verify the server is working correctly before generating images. This does NOT consume API quota - it's a free diagnostic check. Args:
Returns: Server health status, configuration check, and available tools. Use when:
|
| seedream_submitA | Submit an image generation task. Returns immediately - images will appear in the Web App. USE THIS TOOL ON CLAUDE.AI - The regular seedream_generate tool times out on Claude.ai. This tool returns immediately after submitting the task. After submitting: View your generated images at https://seedream-gallery.firebaseapp.com Args:
Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
The core image tools are mostly distinguishable: generate creates from text, edit modifies a single image, blend combines multiple images, and variations makes coherent batches. However, seedream_submit duplicates generate/edit/blend behavior with only async execution as the differentiator, which creates real ambiguity about which tool an agent should select.
All tools share the consistent seedream_ prefix and mostly use verb-style suffixes (edit, generate, blend, submit). variations and status are noun suffixes, which is a minor deviation, but the overall pattern remains predictable and readable.
Six tools is a reasonable size for an image generation server, and most tools serve a distinct purpose. However, seedream_submit largely overlaps with the other image tools and exists primarily as a compatibility workaround, making the set feel slightly padded.
The server covers the main image workflows well: generation, editing, blending, variations, and health checking. The notable gap is that seedream_submit offers no MCP-based way to poll for results or retrieve submitted task outputs programmatically, forcing users to check an external web app.