Runway has two MCP servers, one for the dev portal; Sume has one URL

Runway runs two separate MCP servers, so connecting the wrong one is an easy mistake, while Sume has a single hosted endpoint, https://mcp.sume.com/mcp, that covers account, catalog, jobs, assets, generation and crawl tools. If you came for generation, point your client at the generation server on Runway or at Sume's one URL.

The Runway side is from its MCP guide; the Sume side is from the MCP overview and OAuth pages.

Runway's two servers

Sume's one server

Choosing

Hosted MCP does not have full parity with the HTTP API, so use tools_list and tools_schema for the live contract rather than assuming. Sume's docs also say the Studio Agent product surface is not a public MCP connector, so there is one remote server to configure.

• One URL means one OAuth consent and one set of scopes to review.
• Read-only discovery (tools_list, catalog_list, jobs_list) works under the default mcp:read grant.
• Paid tools such as generate_image and generate_video need mcp:write or an API key, plus an idempotency_key.
• The OAuth consent page lives on the MCP host, so an allowlist for that origin is part of setup.

If you use both vendors

Give each server a distinct name in your client, for example one for Runway's generation server and one for Sume, so the agent can tell which tool belongs where. Never reuse an OAuth token across servers; Sume's docs say an MCP OAuth token is not a Sume API key and should not be forwarded to third parties.