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_videoC | Create a Seedance task on RunAPI (text to video). Returns a task id, status, and output URLs. |
| get_taskB | Fetch the current status and latest result payload for a seedance task. |
| check_pricingC | 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 targets a distinct action: create task, fetch status, check pricing, authenticate. There is no overlap in purpose or resource.
Three tools use snake_case verb_noun or action phrases (get_task, check_pricing, text_to_video), while login is a bare verb without noun. Still readable and largely predictable.
Four tools is well-scoped for a focused text-to-video service, covering the essential workflow without unnecessary bloat.
Core operations (create, poll, price, auth) are present, but lifecycle management like cancel/delete task or list tasks is missing. Minor gaps that agents can work around.