seedance-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key. Can also be stored in ~/.config/runapi/config.json. |
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. |
| text_to_videoB | Create a Seedance task on RunAPI (text to video). Returns a task id, status, and output URLs. |
| get_taskA | Fetch the current status and latest result payload for a seedance task. |
| check_pricingA | Look up RunAPI pricing for the seedance 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 4 tools
Each tool serves a clearly distinct purpose: authentication, task creation, status retrieval, and pricing lookup. There is no overlap or ambiguity between them.
Tool names follow a consistent snake_case pattern with verb-first or noun-verb structure (login, get_task, check_pricing). text_to_video deviates slightly as a noun phrase, but it remains predictable and readable, so minor inconsistency only.
Four tools is well-scoped for a text-to-video generation server. Each tool is necessary for the core workflow (auth, create, fetch status) plus pricing, without redundancy or bloat.
The core lifecycle of text-to-video is covered: authentication, task creation, and status polling. Missing cancel or list operations, but these are not essential for the primary use case, and pricing adds value. Minor gap only.