Railway

Clanker supports Railway inventory, deployment, domain, environment, variable, log, and analytics workflows.

Use clanker railway for direct resource operations, or clanker ask --railway for natural-language questions grounded in Railway account data.

Authentication

Railway uses an account API token.

railway:
  api_token: ""
  workspace_id: ""

Environment variables:

export RAILWAY_API_TOKEN="..."
export RAILWAY_WORKSPACE_ID="..."

RAILWAY_TOKEN is intentionally not used because it is commonly a project deploy token rather than the account token required by the API.

Querying Railway

clanker ask --railway "what projects are running?"
clanker railway list projects
clanker railway list services --project <project-id>
clanker railway list deployments --project <project-id> --service <service-id>

Supported Resources

clanker railway list supports:

• projects
• services
• deployments
• domains
• variables
• environments
• volumes
• workspaces

Some resources require --project, --service, or --environment.

Operations

clanker railway logs --project <project-id> --service <service-id>
clanker railway analytics --workspace-id <workspace-id>
clanker railway deploy --path .
clanker railway redeploy --deployment <deployment-id>
clanker railway cancel --deployment <deployment-id>

Variable and domain management live under clanker railway variable and clanker railway domain.

MCP

The Clanker MCP server exposes clanker_railway_ask and clanker_railway_list for Railway-aware clients.