Skip to main content

​
Overview

The Railway integration inspects the latest successful deployment of any configured Railway service and can request a redeploy after explicit confirmation.

​
Setup

Install the Railway CLI, then either authenticate it interactively or configure a Railway token:
The setup flow accepts an optional token and default project, service, and environment. The token is used when present; an authenticated Railway CLI can be used without one. Tool calls can override any configured default scope. Environment configuration is also supported:
Verify the local integration with:

​
Tools

​
Inspect a deployment

When a default scope is configured, no parameters are required. Otherwise provide the service scope:
The result includes deployment ID, status, and source commit hash/message when Railway provides them.

​
Redeploy a service

confirm must be explicitly true. Railway reuses the latest deployment and returns its new deployment ID. Commands always use explicit project, service, and environment flags and never write Railway link state into the workspace.

​
Errors and security

  • deployment_unavailable means Railway returned no successful deployment in the inspected history.
  • confirmation_required means redeploy was called without confirm=true.
  • Missing configuration, CLI, or authentication failures return structured errors.
  • Railway tokens are never returned in tool output; Railway commands are non-interactive and errors are redacted.