KlingMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| KLING_DEFAULT_MODE | No | Default generation mode | std |
| KLING_DEFAULT_MODEL | No | Default video model | kling-v2-master |
| KLING_REQUEST_TIMEOUT | No | Request timeout in seconds | 300 |
| ACEDATACLOUD_API_TOKEN | Yes | API token from AceDataCloud | |
| ACEDATACLOUD_API_BASE_URL | No | API base URL | https://api.acedata.cloud |
| KLING_DEFAULT_ASPECT_RATIO | No | Default aspect ratio | 16:9 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kling_generate_with_assetsC | Generate with platform element or voice IDs. Specified V2.6 voices cost 1.68 Credits/second. Ownership is verified by the service. |
| kling_list_modelsA | List all available Kling models for video generation. |
| kling_list_actionsA | List all available Kling API actions and corresponding tools. |
| kling_lip_syncA | Synchronize lip movements in a video to match a given audio track or text. |
| kling_talking_photoA | Animate a portrait photo to match a provided audio track (talking-photo). |
| kling_generate_motionA | Transfer motion from a reference video to a character image. |
| kling_generate_turbo_videoA | Generate V3 Turbo 720p/1080p, 3–15 seconds. Native audio is included with no off switch. Poll kling_get_task. |
| kling_generate_storyboardB | Generate V3/V3 Omni multishot video with optional elements and Omni references. Poll kling_get_task. |
| kling_goods_studioB | Generate product studio video from ref_image and goods_title contents. Poll kling_get_task. |
| kling_video_commerceB | Generate creator/product voiceover from an avatar and speech_script. Poll kling_get_task. |
| kling_get_taskA | Query the status and result of a video generation task. |
| kling_get_tasks_batchA | Query multiple video generation tasks at once. |
| kling_generate_videoA | Generate AI video from a text prompt using Kling. |
| kling_generate_video_from_imageA | Generate AI video using reference images as start and/or end frames. |
| kling_extend_videoA | Extend an existing video with additional content. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| kling_video_generation_guide | Guide for choosing the right Kling tool for video generation. |
| kling_workflow_examples | Common workflow examples for Kling video generation. |
| kling_prompt_suggestions | Prompt writing suggestions for Kling video generation. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools target distinct operations (lip sync, talking photo, motion transfer, extend, task polling), but the generation surface is fragmented across six near-siblings: kling_generate_video, kling_generate_video_from_image, kling_generate_turbo_video, kling_generate_storyboard, kling_generate_with_assets, and kling_goods_studio. The boundary between plain generation and model-specific variants (turbo/storyboard/assets) is only weakly explained. kling_list_models and kling_list_actions also overlap as discovery/reference tools.
Nearly all names follow a kling_verb_noun convention in consistent snake_case with a uniform prefix (list_models, get_task, generate_video, extend_video). The exceptions are kling_goods_studio and kling_video_commerce, which are noun phrases rather than verb-led, plus the redundant 'kling_' prefix on every tool. These are minor deviations rather than a pattern break.
At 15 tools the server sits at the top of the well-scoped band, which is defensible for an API with multiple model tiers and specialized modes. A few tools (generate_turbo_video, generate_storyboard, generate_with_assets) are thin wrappers around model variants that arguably could be parameters. Slight over-fragmentation, but each tool maps to a real distinct endpoint.
Coverage is strong across the generation lifecycle: text/image/motion/storyboard/turbo generation, lip sync, talking photo, extend, plus single and batch task polling. Gaps are minor but real: no cancel/delete task, no list-tasks/history, and no account credit or balance query, which matters given the tool descriptions mention credit costs. Agents can work around these but not without friction.