At a glance
- Availability: Experimental (how to enable).
- Auth: API key.
- Connection: The key comes from
RAILWAY_TOKEN. - Docs: https://docs.railway.com/guides/public-api
Credentials
Set these per environment. See Connect an integration.| Variable | Required | Description |
|---|---|---|
RAILWAY_TOKEN | Yes | Railway account or workspace token (Account Settings > Tokens) Docs. |
Setup
- Sign in to Railway: Go to https://railway.com and sign in (the trial/Hobby plan with one deployed project is sufficient for testing).
- Create an API token: Open Account Settings > Tokens (https://railway.com/account/tokens) and create an account token, or select a workspace to create a workspace-scoped token.
- Set the environment variable: Add the token to your .env as RAILWAY_TOKEN=…
- Verify access: Run List Projects, then use a project ID with Get Project to discover its service and environment IDs.
- The API is GraphQL-only at https://backboard.railway.com/graphql/v2; account and workspace tokens are sent as ‘Authorization: Bearer <token>’
- Project tokens use a different header (Project-Access-Token) and are not supported by this connector - use an account or workspace token
- Results use Relay-style connections; each item is wrapped in an edge with a node field
Tools
| Tool | Access | Description |
|---|---|---|
| List Projects | Read | List Railway projects accessible to the token |
| Get Project | Read | Get a project with its services and environments |
| List Deployments | Read | List deployments filtered by project, service, or environment |
| Get Deployment | Read | Get a deployment by ID, including redeploy/rollback eligibility |
| Restart Deployment | Write | Restart a running deployment |
| Redeploy Deployment | Write | Redeploy an existing deployment (creates a new deployment from it) |
Example prompts
- List the latest Railway deployments for my project and summarize their statuses.
- Find the active deployment of my Railway service and restart it.