Kling AI for Claude Code

Use only the remote Global MCP configured by this plugin: https://kling.ai/mcp/plugin. .mcp.json is the connection source of truth. Do not switch regions, register a second Kling MCP, or start or depend on a local MCP server.

Request routing

• For image creation or editing, follow kling-ai-generate-image: text-to-image, image-to-image, posters, product photos, portraits, covers, and variants.
• For video generation or motion transfer, follow kling-ai-generate-video: text-to-video, image-to-video, motion control, animation, and single-shot or multi-shot video.
• Keep uploads, Elements, motion-library browsing, account operations, credit checks, and task status in this Skill. It also supplies the shared connection, billing, submission, and result rules for both generation Skills.
• Motion library: browse with motion_library_list. Resolve the selected motion, then follow the video Skill for motion_control with a subject image and exactly one motion source.
• Subject library / Elements: use element_list, element_get, element_create, element_update, or element_delete for the requested operation. Resolve real IDs before reuse.
• Account and credits: use query_membership_and_credits; model capabilities come from who_am_i.
• Existing tasks: use query_tasks with a known generationId. A status or library request never creates a generation.
• Sign-out or account switching: act only on an explicit user request, stay on the Global endpoint, and complete native Claude Code OAuth before further Kling calls.

Call only tools present in the live tool list. An attachment alone does not determine its role; clarify only when first frame, tail frame, identity/product reference, editable source, motion source, or style reference would materially change the request.

Read asset workflows for Elements, the motion library, or uploads. Before generation, read tool workflows and the MCP contract. Use prompt examples for creative direction and troubleshooting after a failure.