kling-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key. If not set, the server will look for the key 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. |
| ai_avatarC | Create a Kling task on RunAPI (ai avatar). Returns a task id, status, and output URLs. |
| edit_videoC | Create a Kling task on RunAPI (edit video). Returns a task id, status, and output URLs. |
| extend_videoC | Create a Kling task on RunAPI (extend video). Returns a task id, status, and output URLs. |
| image_to_videoB | Create a Kling task on RunAPI (image to video). Returns a task id, status, and output URLs. |
| motion_controlB | Create a Kling task on RunAPI (motion control). Returns a task id, status, and output URLs. |
| text_to_videoB | Create a Kling 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 kling task. |
| check_pricingC | Look up RunAPI pricing for the kling 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
The generation tools (text_to_video, image_to_video, motion_control, ai_avatar, edit_video, extend_video) share near-identical descriptions differing only by the parenthetical task type, but their names clearly signal distinct modalities. login, get_task, and check_pricing are cleanly separate. Only mild overlap between the many generation variants.
Nearly all names use snake_case, and the generation tools follow a consistent verb/resource-to-resource pattern. Slight inconsistency between imperative verbs (login, get_task, check_pricing) and the descriptive generation names, but nothing confusing.
Nine tools is well-scoped for a video-generation API: one auth, one status lookup, one pricing, and six distinct generation modes. Each tool earns its place.
The surface covers auth, all major generation modes, task lookup, and pricing, but lacks task lifecycle management such as listing tasks, canceling, or deleting a task. Agents can poll get_task but cannot enumerate or abort tasks.