railway agent setup defaults new installs to the remote CLI proxy

Introduced 2026-08-13 · score 0.97

HOW TO USE IT

For a new Railway agent install, run `railway setup agent -y` to configure the remote MCP proxy using your CLI login. Use `--local` to select the local GraphQL-backed server, or `--oauth` for editor OAuth.

WHY THIS HELPS

Configure Railway MCP for a coding agent during a new agent install.

BEFORE THIS CHANGE

New agent installs defaulted to the local in-process `railway mcp` server.

REQUIREMENTS AND LIMITATIONS

• Version: v5.39.0
• -y: Runs agent setup without interactive prompts.
• --local: Selects the local GraphQL-backed MCP server instead of the default remote proxy.
• --agent <agent>: Selects the target agent tool; `cursor` is shown in the documented example.
• --oauth: Not documented in the v5.39.0 README or source pages read.
• Prerequisite: Install the Railway CLI; the README's agent install command is `bash <(curl -fsSL railway.com/install.sh) --agents -y`.
• Prerequisite: Authenticate with a Railway account using `railway login` before using the CLI.
• This changes defaults for new agent installs and voluntary setup/install reruns; bare `railway mcp` remains local.
• `--remote` remains a compatibility alias for the new default.

FIRST-PARTY EVIDENCE

• https://github.com/railwayapp/cli/releases/tag/v5.39.0
• https://github.com/railwayapp/cli/pull/1094
• https://github.com/railwayapp/cli/blob/v5.39.0/README.md

Check the installed version and the source before using it. Entry JSON

Report a problem with this card