Manage Workers, R2 buckets, DNS, and edge policies on Cloudflare.
- Home
- Top MCPs for Web Hosting
- Railway
Railway
Spin up Railway projects, services, and deploys via remote MCP with OAuth.
Quick answer
What it does
Surfaces Railway's control plane as MCP tools over a hosted HTTP endpoint: projects, services, deployments, environment variables, and a delegated agent tool.
Best for
- Zero-config remote MCP setup
- OAuth-based team installs
- Quick project + service creation
- Triggering redeploys from chat
Not for
- Workflows that require the full local CLI surface
- Self-hosted MCP needs (this one is hosted)
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "railway": { "command": "claude", "args": [ "mcp", "add", "--transport", "http", "railway", "https://mcp.railway.com" ] } } }Paste under mcpServers. Fully quit and reopen Claude after editing.
CLI or .mcp.jsonshellclaude mcp add railway -- claude mcp add --transport http railway https://mcp.railway.comRun from your repo. Commit .mcp.json to share with your team.
.cursor/mcp.jsonjson{ "mcpServers": { "railway": { "command": "claude", "args": [ "mcp", "add", "--transport", "http", "railway", "https://mcp.railway.com" ] } } }Global path: ~/.cursor/mcp.json. Reload window after editing.
.vscode/mcp.jsonjsonc{ "servers": { "railway": { "command": "claude", "args": [ "mcp", "add", "--transport", "http", "railway", "https://mcp.railway.com" ] } } }VS Code uses the "servers" key (not "mcpServers").
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "railway": { "command": "claude", "args": [ "mcp", "add", "--transport", "http", "railway", "https://mcp.railway.com" ] } } }Open via Cascade → hammer icon → Configure.
cline_mcp_settings.jsonjson{ "mcpServers": { "railway": { "command": "claude", "args": [ "mcp", "add", "--transport", "http", "railway", "https://mcp.railway.com" ] } } }Open via the Cline sidebar → MCP Servers → Edit.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "claude", "args": [ "mcp", "add", "--transport", "http", "railway", "https://mcp.railway.com" ] } } ] } }Continue uses modelContextProtocolServers with a transport block.
~/.codex/config.tomlshell# ~/.codex/config.toml [mcp_servers.railway] command = "claude" args = [ "mcp", "add", "--transport", "http", "railway", "https://mcp.railway.com", ]Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "railway": { "command": { "path": "claude", "args": [ "mcp", "add", "--transport", "http", "railway", "https://mcp.railway.com" ] } } } }Zed calls them "context_servers". Settings live-reload on save.
ChatGPT → Settings → Connectors (remote URL)json{ "name": "Railway", "transport": "http", "url": "https://mcp.railway.com" }Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled. ChatGPT supports remote HTTPS MCP servers only — stdio servers must be hosted on a public HTTPS endpoint first.
- 2
Set required secrets
No credentials required — this MCP runs over stdio without authentication.
- 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. web hosting work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-web-hosting
Compare Railway MCP vs [Fly.io MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/railway - top-mcps.com listing for Fly.io
Install the Railway MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/railway (fetch https://top-mcps.com/mcp/railway.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Web Hosting MCPs
Other tools in the same category worth evaluating.
Compared with Railway
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Web Hosting? See all Web Hosting MCPs →