Runway MCP plus Sume MCP in one Claude Code setup: who does what

Yes: an MCP client such as Claude Code keeps a list of servers, so you can connect Sume's hosted MCP next to the Runway MCP and let the agent choose a tool per job. They are two independent servers with their own sign-in and billing. Runway's changelog says that on 2026-09-18 four Kling video models became available on Runway MCP for paid plans. Sume's hosted server exposes generate_video, kling-motion-control_create and the other generation tools listed in its docs.

Runway's side comes from the Runway changelog, read on 2026-10-02. Sume's side comes from the MCP quickstart, the MCP overview and tools and gates. Neither company describes the other as a partner, and this post does not claim any shared integration.

What did Runway add on 2026-09-18?

The changelog entry lists four Kling models on Runway MCP. It states they need a paid Runway plan.

How do you add the Sume server?

Sume's quickstart gives two commands for Claude Code. Add the Runway server by following Runway's own instructions; the Sume side is:

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

Which jobs should go to which server?

There is no rule from either vendor, so split by what you need. These are practical criteria, not rankings:

• A Kling model name that exists only on Runway MCP (O3 4K, O3 Standard): use the Runway server. Sume lists kling-3 and the Kling 3.0 Motion Control route, not those names.
• A clip you want billed to a Sume wallet and read back as a Sume job: call generate_video or kling-motion-control_create on the Sume server.
• Anything that mixes steps, such as generate, caption, then assemble: the Sume server also carries timeline_create and the caption and trim tools, so the whole chain stays in one job history.

What should you check before letting an agent spend?

Sume's default OAuth consent is read-only (mcp:read); paid tools such as generate_video return insufficient_scope until you turn on write access at the consent page. Paid and write calls need an idempotency_key. Ask the agent to call tools_list once and read what it can reach. Do the same on the Runway side, since each server has its own permissions and its own charges.