Kling MCP: use Kling 3.0 from Claude Code or Cursor

Kling's own developer docs offer a Kling AI Skill that agents such as Claude Code, Cursor and Codex can use. To call Kling 3.0 over MCP instead, connect a remote MCP server that carries the model: fal, Higgsfield, Runway and Sume each name Kling on their MCP pages, and on Sume's hosted server generate_video with model: "kling-3" runs Kling Video v3 Pro.

Sume's side comes from its MCP overview, MCP quickstart, Video generation docs, the API reference and current catalog code; the other options come from their own pages. All were read on 2026-09-28. Sume has no official Kling connector, and the basics page says hosted MCP still works but is not the primary path today: a backend calls POST /v1/videos, as Kling 3.0 API shows.

Which MCP servers can run Kling 3.0?

Kling 3.0 is a model, so the question is which server or agent tool carries it. Each option below signs you in to a different account and bills that account:

How do I add Kling to Claude Code over MCP?

For Sume, add the server over HTTP and sign in:

Default sign-in is read-only (mcp:read), and paid tools return insufficient_scope until you turn Write on at consent. An API-key session sees the full hosted tool set. Cursor and Codex point at the same URL; Sume MCP server for Claude Code, Cursor and Codex has their config.

claude mcp add --transport http sume https://mcp.sume.com/mcp
claude mcp login sume

What does a Kling 3.0 call look like?

Every generation field goes inside payload. Without payload.model, generate_video routes to sume/auto, so name kling-3. Paid tools require an idempotency_key, and dry_run: true previews admission and cost without submitting:

Send it again without dry_run to submit. The tool answers with a job id, not a clip. The agent then calls jobs_wait, which holds at most 55 seconds per call; on wait_slice_expired, retry the wait with the same id and never resubmit the paid create. jobs_result returns the video.

{
  "idempotency_key": "kling-desk-clip-001",
  "dry_run": true,
  "payload": {
    "model": "kling-3",
    "prompt": "slow push-in on a ceramic mug on a desk, morning light",
    "duration": 5,
    "resolution": "720p",
    "aspect_ratio": "9:16"
  }
}

What are Kling 3.0's limits on Sume?

In current catalog code, kling-3 makes 4 to 15 second clips at 16:9, 9:16 or 1:1, from a prompt or from frame_images (a first frame, optionally a last frame), and takes no reference images, videos or audio; Kling 3.0 API lists every field. Over MCP, three more rules apply:

• Read video-router_models before pinning a setting: a parameter the model does not advertise returns a 400.
• Frame images need public HTTPS URLs; hosted MCP cannot read files from your laptop.
• Animating a still with a driving video is a separate tool, kling-motion-control_create; Motion control API covers it.

How much does Kling cost over MCP?

On Sume, video is billed from the workspace USD balance, reserved on submit at provider list × 1.25, plus a 5.5% agent fee by default, and dry_run shows the amount first. kling-3 has a higher per-second rate with audio, and generate_audio defaults to the model's audio capability, so send false for a silent clip. Kling 3.0 API lists both rates, and max_spend_usd caps a call when you send it.

Kling's Skill page says fees are incurred for each submission and that generated assets are kept for 30 days. Higgsfield and Runway draw on that account's credits.