Runway dev MCP login needs Claude Code 2.1.186+; Sume: mcp login

Both Runway's developer MCP and Sume's hosted MCP connect to Claude Code with a claude mcp add command followed by claude mcp login, and neither needs an API key in the config because both use OAuth. The difference is client version: Runway documents terminal login from Claude Code 2.1.186 and a --no-browser option from 2.1.191.

Sume's docs do not mention --no-browser, so for a headless machine, check your Claude Code version and test.

Runway developer MCP

claude mcp add --transport http --scope user runway-dev-mcp https://dev.runwayml.com/mcp
claude mcp login runway-dev-mcp

Sume hosted MCP

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

Differences that matter

• Server name and scope: Runway's example uses --scope user and the name runway-dev-mcp. Sume's quickstart uses the name sume; add a scope flag yourself if you want one.
• Permissions: Sume splits read from write at consent. A read-only session sees read tools only, and a paid tool returns insufficient_scope until you grant write.
• Headless use: for automation without a browser, Sume documents an API key path (Authorization: Bearer or x-api-key) with the full tool set. Paid and write calls still need an idempotency_key.
• Rotate any API key that lands in logs or chat history.

First call

After login, make one cheap read call before anything paid. Runway names whoami; for Sume use mcp_health to confirm the endpoint and auth source, then tools_list. Read the quickstart for Sume hosted MCP for the list of useful first calls.