railway ca imports committed .mcp.json servers into agents

Introduced 2026-08-27 · score 0.93

HOW TO USE IT

When launching a Railway cloud agent from a repository with a committed `.mcp.json`, run `railway ca` there. Its enabled servers are imported with `user-` prefixes, excluding disabled entries and the platform-owned names `railway`, `playwright`, and `railway-machine`.

WHY THIS HELPS

When launching a Railway cloud agent from a repository with a committed `.mcp.json`, carry the repository's MCP server configuration to the agent.

REQUIREMENTS AND LIMITATIONS

• Version: v5.45.0
• Prerequisite: Cloud Agents must be enabled in Priority Boarding; install the Railway CLI and sign in.
• Prerequisite: The repository must have a committed `.mcp.json` for its MCP servers to be imported.
• Import applies when launching from a repo with a committed `.mcp.json`.
• Entries with `disabled: true` and platform-owned names `railway`, `playwright`, and `railway-machine` are excluded from import.
• The VM-side merge is described as add-only.

FIRST-PARTY EVIDENCE

• https://github.com/railwayapp/cli/releases/tag/v5.45.0
• https://github.com/railwayapp/cli/pull/1132
• https://docs.railway.com/cloud-agents/terminal
• https://docs.railway.com/cloud-agents/quickstart
• https://github.com/railwayapp/cli/blob/v5.45.0/src/commands/cloud_agent/mcp_sync.rs

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

Report a problem with this card