Railway
Projects, services and deployments
Railway lets agents list projects and services, create projects, redeploy services, and manage feature flags. Agents can also give multi-step work to the Railway Agent, which reads logs, finds why a deploy failed, creates services and sets variables. Each user signs in to their own Railway account through the browser and chooses the workspaces and projects that agents can use. Agents get full access in those projects: they can deploy staged changes, delete feature flags, and change services, variables, databases and networking through the Railway Agent.
What an agent can do with Railway
See projects and services
The list-projects tool lists the projects that the agent can use, and the list-services tool lists the services in a project. The whoami tool shows the signed-in account. The agent can tell you what runs where before you change it.
Redeploy and ship staged changes
The redeploy tool deploys a service again. The accept-deploy tool commits the staged changes of a project and deploys them. Railway marks accept-deploy as destructive, so that a client can ask you before it runs. The create-project tool makes a new project.
Manage feature flags
The list-feature-flags and get-feature-flag tools read the feature flags of a project. The set-feature-flag tool changes a flag, and the delete-feature-flag tool removes it. Railway marks the delete as destructive.
Give multi-step work to the Railway Agent
The railway-agent tool sends a request in plain language to the Railway Agent. That agent reads build and runtime logs, finds why a deploy failed, creates services, sets variables, connects databases and changes networking and resource limits. Ask it why a backend service crashes on deploy.
How to connect Railway to OpenBot
Open Railway in OpenBot
Press Open in OpenBot on this page, or find Railway in the app's Apps tab. Get the app first if it is not on this computer.
Sign in
Press Connect and finish the sign-in in your browser. OpenBot keeps the token on the computer that runs OpenBot. You can disconnect at any time.
Give an agent a task
Ask an agent for work that needs Railway, such as one of the example prompts below. The agent uses the plugin's tools to do it.
Example prompts3
RailwayWhich projects and services are in my Railway workspace?
Apps1
Railway
Projects, services, and deployments, over Railway's MCP server with browser sign-in.
Information6
- Developer
- Railway
- Category
- Coding
- Version
- 1.0.0
- Website
- railway.com
- Privacy policy
- railway.com/legal/privacy
Questions
Is the Railway MCP server official?
Yes. Railway hosts the Remote MCP Server at mcp.railway.com, with OAuth sign-in. Railway lists its tools in the Railway documentation. Railway also has a local MCP server in its CLI; this plugin uses the remote server.
Does the Railway plugin need an API key?
No. Each user signs in to their own Railway account through the browser and chooses the workspaces and projects that agents can use. The server does not accept project tokens. OpenBot does the sign-in itself, keeps the tokens in encrypted storage, and adds the Authorization header. You can revoke the access in your Railway account settings. The plugin catalog holds no secret.
What can the agent change in Railway?
In the workspaces and projects that you choose, the agent can create projects, redeploy services, deploy staged changes, and change or delete feature flags. Through the Railway Agent, it can also change services, variables, databases and networking. Railway gets the requests that the agent sends. Your workspaces, conversations and files stay on the computer that runs OpenBot.
Does the Railway plugin cost anything?
Installing the plugin in OpenBot is free. You need a Railway account. Railway bills the work of the Railway Agent by the LLM tokens that it uses, with no markup.
Sources
Every statement about Railway comes from the pages below, checked on . They can change after that date.