Runway MCP in Cursor: what shipped and running a second server

Runway's changelog lists "Runway MCP is now available on Cursor's Marketplace" on Sep 23, 2026, for all plans, so you can install it from inside Cursor. Cursor is a general MCP client, so the same settings screen can also hold Sume's hosted MCP server at https://mcp.sume.com/mcp, which is a separate server with its own sign-in.

What did Runway announce for Cursor?

The entry on Runway's changelog, read 2026-09-29, is dated Sep 23, 2026 and is marked "All plans". Its one line says Runway MCP is available on Cursor's Marketplace. The entry gives no tool list or credit rates, so this page does not state any; see Runway MCP for Claude and Cursor for the setup details Runway publishes elsewhere.

How do I add Sume's hosted MCP to Cursor as well?

Sume's quickstart adds a remote MCP server entry in Cursor Settings, or in your MCP config file, with only a URL. Give it its own name so it stays distinct from any other server you installed.

• Complete the OAuth sign-in when Cursor prompts you. Consent happens on the MCP host, not on app.sume.com.
• Call tools_list once afterwards to confirm the session and see which tools it exposes.

{
  "mcpServers": {
    "sume": {
      "url": "https://mcp.sume.com/mcp"
    }
  }
}

What is Cursor allowed to do on Sume?

It depends on the scopes you grant at consent. The default OAuth grant is read-only, so Cursor can list the catalog and read jobs but cannot start a paid generation until you turn Write on.

How do I keep two video servers from being confused?

Name each entry by its vendor, ask Cursor to run tools_list on the Sume server first, and say which server you want in the prompt ("use Sume to generate the clip"). A prompt that only says "make a video" leaves the choice to the client.

Paid and write calls on Sume need an idempotency_key, and generate_video routes to sume/auto when you omit payload.model. Set a model explicitly when you care which one runs; the video docs list the ids and limits, and the hosted MCP overview lists the tools.

What should I check before the first Sume clip?

Limits differ per model, so read them from the catalog instead of assuming one envelope. GET /v1/videos/models lists each model's resolutions, aspect ratios and durations; for example seedance-2.5 accepts 4–30 seconds at 480p, 720p and 1080p, while minimax-h3 accepts 5–15 seconds at native 480p or 768p.

If Cursor drives the generation, ask it to show the estimated cost with a dry run first: the hosted MCP overview notes an optional dry_run that preflights cost on write and paid submits, and an optional max_spend_usd cap. Then let the paid call through once you approve the number.