wan-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 set 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. |
| animateC | Create a Wan task on RunAPI (animate). Returns a task id, status, and output URLs. |
| edit_videoC | Create a Wan task on RunAPI (edit video). Returns a task id, status, and output URLs. |
| image_to_videoC | Create a Wan task on RunAPI (image to video). Returns a task id, status, and output URLs. |
| speech_to_videoB | Create a Wan task on RunAPI (speech to video). Returns a task id, status, and output URLs. |
| text_to_imageB | Create a Wan task on RunAPI (text to image). Returns a task id, status, and output URLs. |
| text_to_videoB | Create a Wan 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 wan task. |
| check_pricingB | Look up RunAPI pricing for the wan 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 9 tools
Most tools have clearly distinct purposes: login, pricing, task status, and six different task creation types. The main potential confusion is between 'animate' and other creation tools, but descriptions clarify the specific task type.
The naming pattern is mostly verb_noun with underscores (get_task, check_pricing, image_to_video, etc.). However, 'animate' breaks the pattern by being just a verb, and 'login' is not verb_noun either, creating minor inconsistency.
Nine tools is well-scoped for a video/image generation server: one auth, one pricing, one status retrieval, and six creation endpoints. Each tool serves a distinct purpose without redundancy.
The core workflow is covered: login, create tasks via multiple modes, and check task status/results. Missing list/cancel/delete operations could be minor gaps, but the main task lifecycle is sufficiently covered.