Railway is launching two new agent-focused features: a Remote MCP Server at mcp.railway.com and a new `railway agent` command in the CLI. The Remote MCP Server connects any MCP-compatible client (Claude, Cursor, Codex, Copilot, etc.) to Railway via OAuth, with no local install required. The CLI command lets developers interact with Railway's AI agent from the terminal, supporting interactive sessions, one-shot prompts, JSON output, and thread continuation. The MCP surface is intentionally minimal (7 tools), with complex multi-step operations delegated to a `railway-agent` tool to preserve context window efficiency. Architecturally, the MCP server is a route handler inside Railway's existing monolith, reusing auth, permissions, and data infrastructure rather than running as a separate service.

14m read timeFrom blog.railway.com
Post cover image
Table of contents
Table of Contents1. Remote MCP Server at mcp.railway.com2. railway agent , the new CLI commandThinking about MCP tool strategyA quick tour inside the engineWhat we want to learn from youStart here
1 Comment

Sort: