At a glance
- Availability: Experimental (how to enable).
- Authentication: API key.
- Connection: The key comes from
RAILWAY_TOKEN. - Provider documentation: Authentication reference.
Credentials
Set these per environment. See Connect an integration.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.
Provider notes
- 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
Verify the connection
Call a read tool such asrailway__list_projects with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.