Railway

About

This is an MCP connector that gives the Sazabi agent tools from Railway's hosted MCP server. Railway authenticates via OAuth with dynamic client registration — you authorize once in the browser and Sazabi refreshes the token thereafter. Access is scoped to the workspaces the connected account belongs to.

What the agent can do:

• Browse projects, services, and environments
• Read deployment status, build logs, and runtime logs
• Inspect and update environment variables
• Trigger and monitor deployments

Prerequisites

• An active Railway account
• Membership in the Railway workspace you want to connect

Set up in the dashboard

Configure connectors in the dashboard under Settings > MCP connectors.

Set up with the CLI

You can also connect Railway with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference).

Railway authenticates over OAuth, so the CLI opens a browser to complete authorization:

sazabi mcp-connectors connect railway

Add --read-only to restrict the connector to read-only tools, or --project-id <project> to target a specific project. In --json mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with sazabi mcp-connectors list.

Verify

Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the connection is authorized.

Troubleshooting

No tools discovered — Disconnect and reconnect from Settings > MCP connectors to restart the OAuth flow.

Connection shows needs attention — The authorization may have expired or been revoked; reconnect from Settings > MCP connectors.

Further reading