@runapi.ai/veo-3-1-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. |
| extend_videoC | Create a Veo 3.1 task on RunAPI (extend video). Returns a task id, status, and output URLs. |
| text_to_videoC | Create a Veo 3.1 task on RunAPI (text to video). Returns a task id, status, and output URLs. |
| upscale_videoC | Create a Veo 3.1 task on RunAPI (upscale video). Returns a task id, status, and output URLs. |
| get_taskA | Fetch the current status and latest result payload for a veo-3-1 task. |
| check_pricingA | Look up RunAPI pricing for the veo-3-1 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
The creation tools (upscale_video, extend_video, text_to_video) have similar descriptions starting with 'Create a Veo 3.1 task on RunAPI', but their names clearly indicate different operations. Login, pricing, and status tools are distinct. Minor ambiguity from identical phrasing.
Most tools follow verb_noun snake_case, but 'login' is a bare verb and 'text_to_video' is not verb_noun. This mixed pattern reduces consistency, though still readable.
6 tools cover the core tasks: three creation types, status retrieval, pricing, and authentication. This is well-scoped for a video generation service.
The set covers create, monitor, and pricing. Missing operations like cancel or list tasks are minor gaps; core workflow is complete.