Connect Runway Dev

Runway Dev lets a coding agent work against your Developer Portal account from the editor: look up tasks, manage model routers, and read docs without copying an API key into mcp.json.

This is separate from the generation MCP at mcp.runwayml.com, which creates media in chat.

Tip

You need a Runway Dev account before connecting. Create one if you have not already.

The server URL is the same in every client:

https://dev.runwayml.com/mcp

Apps display the server as Runway Dev. CLI server identifiers cannot contain spaces, so the commands below use runway-dev-mcp.

Caution

Complete OAuth yourself in your normal browser. Do not ask an agent to automate the sign-in or approval steps.

Cursor

One click adds the server. Cursor then opens a browser to sign in.

Add Runway Dev to Cursor

Or paste this into ~/.cursor/mcp.json (or .cursor/mcp.json in a project) and restart Cursor:

{
  "mcpServers": {
    "Runway Dev": {
      "url": "https://dev.runwayml.com/mcp",
      "auth": {
        "CLIENT_ID": "tpc_txSKrGxCMEUUaNzR8PLdcE"
      }
    }
  }
}

Then open Settings → MCP, find Runway Dev, and connect. Approve access in the browser when prompted.

Claude Desktop

Claude Desktop uses the same custom connectors as Claude.ai. One click opens Add custom connector with the name and URL filled in.

Add Runway Dev to Claude

Claude Code

Claude Code does not use Claude Desktop connectors. Add the server from a terminal:

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

In a session, run /mcp, select runway-dev-mcp, and authenticate.

If Claude Code shows Needs authentication:

1. Run /mcp.
2. Select runway-dev-mcp.
3. Complete authentication in your normal browser.
4. Retry the MCP tool in the same Claude Code session.
5. Request a new session only if the authenticated tools remain unavailable.

Claude Code 2.1.186 or newer can also start authentication from a terminal:

claude mcp login runway-dev-mcp

Claude Code 2.1.191 or newer supports --no-browser. This option prints an authorization URL instead of opening a local browser:

claude mcp login runway-dev-mcp --no-browser

Codex

codex mcp add runway-dev-mcp --url https://dev.runwayml.com/mcp
codex mcp login runway-dev-mcp

Or add the same URL in ~/.codex/config.toml:

[mcp_servers.runway-dev-mcp]
url = "https://dev.runwayml.com/mcp"

Then run codex mcp login runway-dev-mcp to complete browser login.

After you connect

Ask the agent to call whoami. You should see your Developer Portal email. If that fails, authenticate with the client steps above and retry in the same session.

Do not put an API key in the MCP config. Keys stay in the Developer Portal, where you can rotate them.