Railway MCP Server

Add to your client

Copy the config for your MCP client and paste it into its config file.

{
  "mcpServers": {
    "railway-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@jasontanswe/railway-mcp"
      ],
      "env": {
        "RAILWAY_API_TOKEN": "<your-railway-api-token>"
      }
    }
  }
}

Before you start

• Node.js 18+ (required for the built-in fetch API)
• An active Railway account
• A Railway API token, created at railway.app/account/tokens (an account- or team-scoped token)
• An MCP-capable client such as Claude Desktop, Cursor, Cline, or Windsurf

About Railway MCP Server

Tools & capabilities (15)

When to use it

• Use it when you want to spin up a new Railway service from a GitHub repo or Docker image without leaving your editor.
• Use it when you need to set, copy, or bulk-update environment variables across services and environments.
• Use it when you want your agent to trigger a deployment and then tail the deployment logs to debug a failure.
• Use it when you need to provision a managed database (Postgres, Redis, MySQL, Mongo) into an existing project.
• Use it when you want to audit your projects, services, and environments programmatically through an agent.

Quick setup

1. 1Generate a Railway API token at railway.app/account/tokens.
2. 2Add the server to your client config, e.g. command `npx` with args `-y @jasontanswe/railway-mcp` and `RAILWAY_API_TOKEN` set in the env block (Cursor accepts the token as a trailing CLI arg).
3. 3Alternatively run `npx -y @smithery/cli install @jason-tan-swe/railway-mcp --client claude` to auto-configure Claude Desktop.
4. 4Restart your MCP client so it picks up the new server.
5. 5Verify by asking the agent to run `project-list`, or call `configure` to set the token if you did not pass it via env.

Railway MCP Server FAQ