railway

This Railway MCP server integrates with the Railway.app platform to let MCP clients manage Railway resources through natural language prompts. The server supports authentication with Railway API tokens, project management (listing, info, and deletion), deployment control (listing and restarting deployments), service management (creating services from a GitHub repo or a Docker image, and listing services), as well as variable, network, and volume management. With Claude, Cursor, Windsurf, or other MCP clients, you can issue commands like listing your Railway projects, starting or restarting deployments, or provisioning new services directly from chat or a conversational interface. The server translates high-level requests into Railway API calls, enabling you to orchestrate infrastructure without leaving your MCP client.

Prerequisites:

• Node.js 18+ installed on the machine where you run the MCP client
• A Railway account with a valid API token
• An environment where MCP clients can access the server (local machine, server, or cloud VM)

Installation steps:

1. Install the MCP server via the recommended command (handled by MCP clients): npx -y @jasontanswe/railway-mcp

2. If you are configuring via Claude/Desktop, add the server with the following configuration: { "railway": { "command": "npx", "args": ["-y", "@jasontanswe/railway-mcp"], "env": { "RAILWAY_API_TOKEN": "your-railway-api-token-here" } } }

3. If you are manually adding the server in a MCP client configuration file, ensure the token is provided either in the env section or via a secure prompt in the client. Restart your MCP client after adding the configuration.

4. Test a basic command to verify connectivity, for example: "Please list all my Railway projects". If prompted, provide your Railway API token when required.

Prerequisites recap: Node.js 18+, Railway account, and a Railway API token are required before using the railway-mcp server.

Tips and caveats:

• Railway API tokens grant broad access to your account; treat tokens as secrets and prefer environment-variable storage when possible.
• When using the environment variable method, the token will be stored in your MCP client's configuration file; ensure file permissions are restricted.
• If you encounter authentication errors, verify that the token is valid and has the necessary permissions; regenerate tokens if needed.
• Keep the MCP server up to date to ensure compatibility with Railway API changes; periodically check for updates from the MCP client ecosystem.
• For best results, pair this server with MCP clients that have terminal or scripting capabilities to leverage full Railway operations (deploy, move, and monitor services).