seedream-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | Yes | Your RunAPI API key |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json. |
| decompose_layersC | Create a Seedream task on RunAPI (decompose layers). Returns a task id, status, and output URLs. |
| edit_imageC | Create a Seedream task on RunAPI (edit image). Returns a task id, status, and output URLs. |
| text_to_imageB | Create a Seedream task on RunAPI (text to image). Returns a task id, status, and output URLs. |
| get_taskA | Fetch the current status and latest result payload for a seedream task. |
| check_pricingB | Look up RunAPI pricing for the seedream model line. |
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
Each tool has a clearly distinct role: authentication, pricing lookup, task status retrieval, and three separate image-generation modes. The three creation tools are explicitly differentiated by their Seedream task type (decompose layers, edit image, text to image), so an agent should not confuse them.
Most names follow a verb_noun pattern (get_task, check_pricing, decompose_layers, edit_image), but text_to_image is a noun phrase rather than a verb-led action, and login lacks an object. The set remains readable, but the convention is not uniform.
Six tools is well-scoped for a Seedream/RunAPI integration: authentication, pricing, task status, and three generation modes. Each tool has a clear place, with no obvious bloat or thin coverage.
The core lifecycle is covered: login, check pricing, create tasks for all three image operations, and poll task status/results. Minor gaps exist around task management, such as listing tasks, canceling tasks, or logging out/clearing credentials.