What an agent can do in Railway
Create projects, deploy templates, manage environments and variables, and inspect and redeploy Railway services.
Jobs on Rush that use Railway
- Which Railway Projects Are Still Running for Clients We No Longer Serve? A Web Agency's Monthly Hosting Check
- Which Feature Flags Changed or Were Left On This Week? A Restaurant-Ordering Software Company's Monday Flag Review on Railway
How Railway connects
Railway is a remote MCP server, published by Railway, at https://mcp.railway.com. Connecting it signs in through the MCP OAuth flow on Railway's side.
From Railway: Railway's MCP documentation · source code.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names railway in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "Railway",
"url": "https://mcp.railway.com"
}Whose Railway account the agent uses
Your Railway connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Railway, and a run started with an API key uses the Railway of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Railway, and that agent's runs use their account and nothing else: never yours, never another user's.
More Cloud integrations
Frequently asked questions
How do I connect Railway to Rush?
Open Settings → Connections in the console and connect Railway, or send POST /me/connections with {"type":"mcp","name":"Railway","url":"https://mcp.railway.com"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my Railway account?
No. A run gets your Railway connection only when it names it in connections ("connections": ["railway"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in Railway?
Create projects, deploy templates, manage environments and variables, and inspect and redeploy Railway services. 2 published jobs use it; this page lists them.
Can my app's users connect their own Railway?
Yes. Make each user an agent from your template, and they sign in to their own Railway through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for engineering teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to