Skip to content
Railway

RailwayMCP Server

by Railway
Released
v0.1.12
MIT
Repository Docs npm
Cloud & Infrastructure

Summary

Railway's official MCP server, bundled with the Railway CLI — 40+ tools for projects, services, deployments, variables, domains and observability, with destructive actions gated behind explicit confirmation.

Features

  • 40+ local tools across projects, services, environments, deployments, variables, domains, networking, templates and storage
  • Observability tools for logs, metrics, request analysis and error rates
  • Remote server at mcp.railway.com with a railway-agent tool for multi-step debugging
  • Destructive operations require an explicit confirm: true
  • OAuth or CLI-proxied auth; project tokens are not accepted for remote MCP

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Railway" tools will be available.
{
  "mcpServers": {
    "railway-mcp": {
      "command": "railway",
      "args": [
        "mcp"
      ]
    }
  }
}

Description

Railway's official MCP server gives an agent operational control of a Railway account: the projects, services and environments in it, the deployments running, the variables and domains configured, and the logs and metrics coming out. It is distributed with the Railway CLI rather than as a standalone package — the earlier @railway/mcp-server npm build is deprecated in favour of railway mcp.

Local and remote are different servers

This is the detail worth knowing before wiring it up.

Local MCP runs through the CLI on your machine, reusing the credentials from railway login. It is the full surface: roughly 40 tools spanning account, projects, services, environments, deployments, variables, domains, networking, templates and storage, plus observability tools for logs, metrics, request analysis and error rates.

Remote MCP runs at mcp.railway.com and exposes a deliberately narrower set — account, projects, feature flags and deployments — plus a railway-agent tool that handles multi-step work like log analysis, debugging and service configuration on the server side. It authenticates by direct OAuth, or through the CLI acting as a proxy for your existing login. Project tokens are not accepted; remote MCP requires a user identity.

Safety model

Destructive operations carry protocol-level hints and require an explicit confirm: true before they execute, so a deletion cannot fall out of a single ambiguous instruction. Remote MCP issues short-lived OAuth tokens and marks destructive actions for client-side confirmation. Railway's own guidance is to review anything an LLM proposes against a production environment before approving it.

Setup

railway setup agent configures the local server; --remote switches to the CLI-proxied remote server and --remote --oauth to a direct OAuth connection. railway mcp install does per-editor configuration by hand. Cursor, VS Code, Claude Code and Windsurf are documented as supported clients.

Related MCP Servers

MCP: AWS MCP Server

by Amazon Web Services

New

AWS's managed MCP server: call any AWS API, run sandboxed Python against your account, and load AWS agent skills on demand — under IAM, CloudWatch and CloudTrail.

Cloud & Infrastructure

MCP: gcloud MCP Server

by Google

Featured

Google's official MCP server for driving the gcloud CLI from natural language, with allowlist and denylist controls over which commands an agent may run.

Cloud & Infrastructure
2 views
Browse all MCP servers →