@railway/mcp-server

What it does

This package is a compatibility shim for the deprecated standalone Railway MCP server. It now delegates to the Railway CLI's built-in MCP implementation. The actual MCP server—which provides structured access to Railway's deployment and infrastructure APIs—is bundled into the Railway CLI and invoked via the railway mcp command. This shim ensures existing configurations continue to function while encouraging migration to the CLI-native approach.

Who it's for

Teams deploying on Railway who want to integrate Claude with their infrastructure workflow. Rather than maintaining a separate npm package, Railway consolidated MCP support into the CLI itself, making the integration simpler for new users while preserving backward compatibility for existing setups.

Common use cases

• Query Railway project details, service status, and deployment history from Claude
• Trigger deployments or fetch logs programmatically
• Inspect and manage environment variables and secrets across Railway environments
• Automate infrastructure decisions based on real-time deployment data

Setup pitfalls

• This npm package is deprecated; the Railway CLI is the maintained integration point
• The Railway CLI must be installed; the package exits with migration instructions if missing
• Configs invoking npx -y @railway/mcp-server continue to work but should be updated to call railway mcp directly
• After installing or upgrading the Railway CLI, run railway mcp install to configure MCP; use --remote if you prefer the hosted server