RunAPI Vidu MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | RunAPI API key used for task creation and status polling. The server resolves auth in this order: (1) the RUNAPI_API_KEY environment variable, useful for headless and CI hosts; (2) ~/.config/runapi/config.json, created by the MCP login tool or runapi login; (3) no key, which still allows check_pricing. |
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. |
| image_to_videoB | Create a Vidu task on RunAPI (image to video). Returns a task id, status, and output URLs. |
| reference_to_videoC | Create a Vidu task on RunAPI (reference to video). Returns a task id, status, and output URLs. |
| get_taskA | Fetch the current status and latest result payload for a vidu task. |
| check_pricingC | Look up RunAPI pricing for the vidu 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 5 tools
Each tool maps to a distinct purpose: login, task creation (two variants), task polling, and pricing. The image_to_video vs reference_to_video pair shares the same 'create a Vidu task' framing and could momentarily confuse, but the descriptions clearly distinguish the two input modes.
Most names follow a verb_noun convention (get_task, check_pricing) or a clear X_to_video pattern shared by the two generation tools. login is a bare verb that breaks the pattern slightly, but the set remains readable and predictable overall.
Five tools is well-scoped for a video-generation API: auth, two generation modes, polling, and pricing. Nothing feels redundant, though the surface is on the leaner side.
Core workflow (login, create task, poll task, check pricing) is covered, but there is no tool to list existing tasks, cancel a task, or access other plausible Vidu modes (e.g. text-to-video). get_task partially compensates but leaves dead ends for task management.