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_avatarB | Create a Kling task on RunAPI (ai avatar). Returns a task id, status, and output URLs. |
| extend_videoB | 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_controlC | 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_pricingB | 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 8 tools
Each tool has a clearly distinct purpose: login for authentication, five different video generation types (ai_avatar, extend_video, image_to_video, motion_control, text_to_video), get_task for status retrieval, and check_pricing for cost lookup. No overlap in functionality.
All names use lowercase with underscores, but the pattern is inconsistent: some are verb_noun (extend_video, get_task, check_pricing) while others are just task type names (ai_avatar, image_to_video, motion_control, text_to_video). This mixed convention could cause minor confusion about which are actions vs. resource types.
With 8 tools, the server covers authentication, five distinct generation operations, status retrieval, and pricing. This is a reasonable scope for a video generation API, though slightly on the higher side but still well-scoped.
Core operations are present: login, generation, status, pricing. However, missing cancel or delete for tasks, and there is no listing of past tasks. These gaps may force agents to rely on external tracking or default to polling, limiting workflow completeness.