Set up Runway Dev

Guide the user from plugin installation to a connected Developer Portal account. This skill is included with the plugin; use it directly and do not install or fetch a duplicate copy.

First check whether the bundled Runway Dev MCP is already connected. If whoami succeeds, skip sign-in and continue with project selection. If the server is configured but needs authentication, use the host's connection flow rather than adding another server entry.

1. Sign in or create an account

Ask whether the user already has a Runway Dev account only if that is not clear from the conversation. Send them to the Runway Dev Developer Portal: they can sign in with an existing account or create one there. Let the user complete any sign-up, verification, and consent steps themselves in their browser. Do not automate the browser authentication or create an account on the user's behalf.

If they are building an application integration, explain that Developer Portal access alone does not configure the application. They may need to select or create a project and create a project API key in the portal. Follow API setup for current project and key steps. Do not request that the user paste the key into chat.

2. Connect Dev MCP

Connect the host to https://dev.runwayml.com/mcp using the host's documented MCP setup at Connect Runway Dev. MCP uses browser OAuth. The application SDK uses a separate project API key; never put that key in MCP configuration.

If the MCP server is not configured, help add it using the exact configuration format documented for the user's host. Do not assume every host supports the same plugin-install flow or command. If the host is unknown, link the connection guide and ask which host they are using before editing host-specific config.

When prompted, have the user complete Runway OAuth in their normal browser, return to the same agent session, and retry the MCP check. Never ask for their Runway password, OAuth code, or API key.