Railway

Connecting Railway lets an agent confirm a deploy actually went out and the service stayed healthy afterwards, rather than assuming the merge was the end of it.

Before you start

You need a Railway account with access to the workspace and project you want agents to see. Railway's own guide is MCP server.

There is no token to create, and Railway does not accept project tokens for this: the connection needs a user identity for billing and audit. You authorize it by signing in to Railway in your browser, and you choose which workspaces and projects SetForth may reach.

Connect it

1. In SetForth, open your project, then Integrations.
2. Choose Railway.
3. Leave the server URL as https://mcp.railway.com.
4. Choose Connect. You go to Railway, sign in, and choose which workspaces and projects SetForth may reach.
5. Railway sends you back to SetForth and the integration is connected.

Railway issues short-lived tokens and you can revoke SetForth's access at any time from your Railway account settings.

Railway also holds back some data from connected apps regardless of what you approve. An agent can list a service's environment variables by name, for example, but never sees their values.

What agents can check

Connecting a deploys and infrastructure tool adds one follow-up:

• Verify deploy health checks the deployment for a task's release once it has had time to finish. You name the service and environment, and how long to wait.

Who the connection belongs to

The connection carries the access of whoever authorized it. Its page in SetForth shows who that was. If they leave or lose access in Railway, the integration stops working and Reconnect hands it to someone else.