railway mcp

Let Claude and other MCP clients manage your Railway.app infrastructure. Deploy services, manage variables, and monitor deployments - all through natural language.

A Model Context Protocol (MCP) server for integrating with the Railway.app platform.

Table of Contents

Features • Installation • Available Tools • Example Workflows • Security • Troubleshooting • Contributing

Features

• ✅ Authentication with Railway API tokens
• ✅ Project management (list, info, delete)
• ✅ Deployment management (list, restart)
• ✅ Service management (create from GitHub repo or Docker image, list)
• ✅ Variable management (list, create/update, delete)
• ✅ Service Network management
• ✅ Volume management
• ❌ Full support for all templates
• ??⏳ Database template support
• Automatic database and networking workflows
• ??⏳ Most commonly used workflows
• ❌ Automatic GitHub repository linking for services

Installation

Prerequisites

• Node.js 18+ (for built-in fetch API support)
• An active Railway account
• A Railway API token (create one at https://railway.app/account/tokens)

Quick Start

This MCP server is designed to work with MCP Clients like: - Claude for Desktop | ✅ Battle-Tested - Cursor | ✅ Needs Testing - Cline | ??⏳ Needs Testing - Windsurf | ??⏳ Needs Testing - Other MCP Clients | ??⏳ Needs Testing

Installing via Smithery

To install railway-mcp automatically, we recommend using Smithery

Claude Desktop

npx -y @smithery/cli install @jason-tan-swe/railway-mcp --client claude

Cursor

npx -y @smithery/cli@latest run @jason-tan-swe/railway-mcp --config "{"railwayApiToken":"token"}"

npx -y @jasontanswe/railway-mcp <RAILWAY_API_TOKEN>

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

{
  "mcpServers": {
    // ... All of your existing MCP servers ...

    // Add the railway-mcp server to your configuration with your API token
    "railway": {
      "command": "npx",
      "args": ["-y", "@jasontanswe/railway-mcp"],
      "env": {
        "RAILWAY_API_TOKEN": "your-railway-api-token-here"
      }
    }
  }
}

Please list all my Railway projects

Please configure the Railway API with my token: {YOUR_API_TOKEN_HERE}

Recommendations and Other Information

This server best combines with MCP-clients that have access to terminal or with Git (Cursor, Windsurf). Using this MCP with others is recommended as railway-mcp orchestrates containers and streamlines your deployment process seamlessly.

Recommended MCP servers to combine with

• Git || Official Link
• GitHub || Official || Smithery

For Claude

• Out of the box, Claude does not have terminal access, so it cannot trigger deployments as it will not be able to get the latest commit.
• Spinning up different services and monitoring them are the best use case with Claude.

For Cursor

• Use with GitHub MCP or have the repository already setup on GitHub and cloned locally on your machine to leverage full integration with railway-mcp.
• When Cursor makes a change, it may forget to push it's changes to GitHub causing it to try and deploy a commit that Railway cannot pull.
• SOLUTION: Always ask or include somewhere in your prompt: Have you pushed our changes to GitHub yet?

Security Considerations

• Railway API tokens provide full access to your account. Keep them secure.
• When using the environment variable method, your token is stored in the Claude Desktop configuration file.
• Sensitive variable values are automatically masked when displayed.
• All API calls use HTTPS for secure communication.
• The server's memory-only token storage means your token is never written to disk outside of the configuration file.

Troubleshooting

If you encounter issues:

1. Token Authentication Issues
2. Ensure your API token is valid and has the necessary permissions
3. If using the environment variable method, check that the token is correctly formatted in the config file

4. Try using the configure tool directly in Claude if the environment token isn't working

5. Server Connection Issues

6. Check that you've installed the latest version of the server
7. Verify that Node.js version 18 or higher is installed

8. Restart Claude for Desktop after making changes to the configuration

9. API Errors

10. Verify that you're using correct project, environment, and service IDs
11. Check Railway's status page for any service disruptions
12. Railway API has rate limits - avoid making too many requests in a short period

Contributing

We welcome contributions from the community! Please see our Contributing Guidelines for details on how to get started, development guidelines, and debugging information.

Available Tools