railway mcp proxy bridges stdio to the remote MCP server using CLI login

Introduced 2026-07-27 · score 0.97

HOW TO USE IT

When the repository workflow already has a stored `railway login`, run `railway mcp proxy` to connect the editor over stdio to Railway’s remote MCP server using CLI authentication.

WHY THIS HELPS

Connect an MCP-capable editor to Railway’s remote MCP server when the repository workflow already uses `railway login`.

BEFORE THIS CHANGE

The editor connected directly to `mcp.railway.com` and used its OAuth flow.

REQUIREMENTS AND LIMITATIONS

• Version: v5.30.0
• Prerequisite: Requires Railway CLI authentication from `railway login`.
• Requires an existing stored `railway login`.
• Token freshness uses `ensure_valid_token`, the same lockfile-serialized refresh used by the rest of the CLI.
• Docs conflict: Current Railway docs say `proxy` behaves like bare `railway mcp`; on CLI versions before 5.44.0, bare `railway mcp` starts the in-process server. This differs from the v5.30.0 proxy behavior described by the release note. https://docs.railway.com/cli/mcp

FIRST-PARTY EVIDENCE

• https://github.com/railwayapp/cli/releases/tag/v5.30.0
• https://github.com/railwayapp/cli/pull/1026
• https://docs.railway.com/cli/mcp

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

Report a problem with this card