Railway

Cancel a Railway deployment that is queued or building, preventing that in-progress deployment from completing. This does not stop a running deployment and requires confirm=true.

Collect a bounded, best-effort Railway deployment evidence bundle from live-validated deployment, snapshot, event, service-instance, log, and metric sources. Results may be partial and report completeness and errors for each source. This tool performs no AI reasoning or root-cause diagnosis and does not modify code or open pull requests.

Commit existing staged changes for a Railway environment, completing a staged STAGE_TEMPLATE or create-environment workflow. This irreversible update can start deployments unless skip_deploys=true and requires confirm=true.

Commit an explicit Railway patch for bucket creation, updates, or deletion and the environment private-network enabled state. Existing staged changes are not committed or replaced, and this tool does not change services, variables, or volumes. Bucket deletion is irreversible and requires confirm_destructive=true.

Create either a generated railway.app domain or a caller-owned custom domain. Custom-domain responses include every DNS setup record plus Railway's verification token and state.

Create an empty Railway environment or clone an existing environment, with explicit initial-deployment and change-staging behavior.

Creates a new plugin in Railway for the specified project. Use this action when you need to add a custom plugin to a Railway project, such as for integrating external services or extending project functionality. The action requires a valid project ID (found in the Railway dashboard URL) and a descriptive name for the plugin. The plugin will be created with default settings and can be further configured after creation.

Create a Railway project in an accessible workspace and return its project and default-environment IDs. Optionally connect a repository branch for deployment and configure the runtime, public visibility, and pull-request deployment settings.

Create an empty, repository-backed, image-backed, or template-backed service in a Railway project.

Create a persistent Railway volume and optionally attach it to one service and environment. This action creates billable persistent state and does not clean it up; deletion is a separate DELETE_VOLUME action that requires workspace-admin authorization when using OAuth.

Permanently delete a completed Railway deployment from deployment history and stop any remaining project usage from it. This does not delete the service, is irreversible, and requires confirm=true.

Permanently delete one generated Railway domain or custom domain by ID after explicit confirmation.

Permanently delete one Railway environment and its deployments. This action is irreversible, requires confirm=true, and requires workspace-admin authorization when using OAuth. Reconnect with a separately selected workspace:admin grant if Railway returns Not Authorized.

Delete a Railway environment variable. This action uses the `variableDelete` GraphQL mutation to permanently remove an environment variable from a project, environment, or service. This action is irreversible — once deleted, the variable cannot be recovered.

Permanently delete a persistent volume and all its associated data from Railway. Use when you need to remove a volume that is no longer needed. This action is irreversible — the volume and all its data will be permanently deleted and cannot be recovered once removed. Use this action when: - Cleaning up unused volumes to reduce storage costs - Removing volumes associated with deprecated environments - Deleting volumes before removing a project

Delete a Railway workspace and all data associated with it. This action uses the `workspaceDelete` GraphQL mutation to permanently remove a workspace. Use this action when you need to permanently delete a workspace that is no longer needed. This action is irreversible — once deleted, the workspace and all its associated projects, environments, and data cannot be recovered.

Start a Railway deployment from a service's already connected repository or image source, optionally at a repository commit SHA, and return the deployment ID. This action cannot access or upload local files; connect the source to the service before calling it.

Deploy a complete Railway template configuration into a new project or an existing project environment. Railway commits the template changes and starts their deployments.

Disconnects the authenticated user's Railway account from Discord. Use when you need to unlink a Discord account that was previously connected to Railway for notifications, authentication, or team management. This action is irreversible for the disconnect operation — the user must manually reconnect through the Railway dashboard or Discord OAuth flow if needed.

Return a bounded, optionally filtered time window of build-phase logs for one Railway deployment.

Return one deployment's status, timestamps, metadata, and rollback eligibility.

Retrieve runtime logs for a deployment. Use when you need to view the runtime application logs for troubleshooting runtime issues, monitoring application behavior, or debugging errors that occur during deployment execution. This action queries the Railway GraphQL API for runtime log entries associated with the specified deployment ID. The logs are returned in reverse chronological order (most recent first).

Get details of a specific Railway environment by its ID, including service instances and deployment information. Use this action when you need to retrieve detailed information about an environment, such as its name, creation timestamp, and the service instances deployed within it, along with their latest deployment statuses. This is a read-only action that queries the Railway GraphQL API.

Get information for a GitHub pull request associated with a Railway service. Use this action when you need to retrieve details about a specific pull request, such as its title, state, URL, or author information, for monitoring PR status or integrating with CI/CD workflows. This is a read-only action that queries the Railway GraphQL API for pull request information linked to the specified service.

Return a bounded date-anchor window of HTTP request logs for one deployment, including request, response, timing, and routing fields.

Return either HTTP request counts grouped by status code or p50/p90/p95/p99 response-time series for one Railway service and environment. Status counts are returned as evidence and are not converted into an error percentage.

Return sampled CPU, memory, disk, network, backup, or volume measurements for selected Railway resources and time range.

Return a Railway template's ID, name, and serialized configuration required for deterministic deployment.

Get the total kickback earnings for the authenticated Railway user. Use this action when you need to retrieve the kickback earnings information for the authenticated user, including the total amount earned and the currency. This is a read-only operation that queries the Railway GraphQL API. Kickback earnings are rewards earned through the Railway referral program when users you refer upgrade their Railway projects.

Retrieve all API tokens for the authenticated user from Railway. Use this action when you need to fetch the list of API tokens associated with the currently authenticated user. This is a read-only operation that returns token metadata including the ID, name, and creation timestamp for each token. The action queries the Railway GraphQL API and returns the complete list of tokens.

List one page of Railway deployments filtered by project, environment, service, status, or deletion state.

List Railway and custom domains for a service, including IDs, ports, DNS records, certificate state, and custom-domain verification token.

Retrieve all patches for a Railway environment using the GraphQL API. Use this action when you need to fetch the list of configuration patches applied to an environment. This is useful for auditing environment history, tracking configuration changes, or reviewing past deployments to an environment. The action queries the Railway GraphQL API for all patches associated with the specified environment ID and returns their metadata including identifiers and timestamps.

List one page of project environments with IDs, pull-request metadata, source environment, and staged-change count.

Retrieve a list of GitHub repositories that Railway has access to. Use this action when you need to fetch the list of GitHub repositories associated with the authenticated user's GitHub account through Railway. This is a read-only operation that returns the id, name, and owner for each repository. The action queries the Railway GraphQL API githubRepos endpoint and returns the complete list of accessible GitHub repositories.

Retrieve the list of GitHub scopes the user has installed the installation to. Use this action when you need to fetch the list of GitHub scope names that the authenticated user has granted to the Railway GitHub application. This is a read-only operation that returns an array of GitHub permission scope strings such as 'repo', 'workflow', or 'read:user'. Note: This endpoint requires account-level authentication, not workspace/project tokens.

Retrieve all integration auths for the authenticated user from Railway. Use this action when you need to fetch the list of integration auths (such as GitHub, GitLab, Vercel, or other connected integrations) associated with the currently authenticated user. This is a read-only operation that returns auth metadata including the ID, name, type, and creation timestamp for each integration. The action queries the Railway GraphQL API and returns the complete list of integration auths.

Retrieve notification deliveries for the authenticated user. Use this action when you need to fetch a list of notification deliveries, such as tracking which notifications have been sent (e.g., EMAIL, WEBHOOK, SLACK) and when they were created. This is a read-only operation that queries the Railway GraphQL API. The action supports pagination through the GraphQL edges/node pattern and returns basic notification delivery information including ID, type, and creation timestamp for each delivery.

List one page of projects in an accessible Railway workspace with project and workspace identifiers. Use LIST_SERVICES and LIST_ENVIRONMENTS for those independently paginated resources.

List one page of service IDs and names in a project for service, deployment, logs, metrics, domain, and volume tools.

Fetch all trusted domains for the authenticated Railway workspace. Use this action when you need to retrieve all trusted domains configured for workspace membership invitations. Trusted domains allow users with emails from those domains to be invited to the workspace without individual invitations. This is useful for auditing existing domain configurations or obtaining domain IDs for deletion operations. This action requires authentication and will return domains from the workspace associated with the provided credentials.

Return Railway shared-environment or service variables. Choose stored to preserve or render references, or deployment_resolved to return the values supplied to a specific service deployment. Variable values may be sensitive.

List one page of persistent volume IDs and names in a project for storage configuration and metrics workflows.

Create a new Railway deployment with the selected deployment's exact code and build/deploy configuration, optionally using its previous image tag. This does not deploy the latest source commit and requires confirm=true.

Rename one environment without changing or deploying its configuration.

Replace the entire Railway shared-environment or service variable collection with the supplied complete map. This is irreversible: every existing variable whose key is omitted from the map is permanently deleted. Railway skips deployments by default; set skip_deploys=false and confirm_deploys=true to explicitly trigger deployments.

Restart a running or crashed Railway deployment by reusing its existing image without rebuilding or creating a deployment from newer source. Requires confirm=true.

Read the corrected Railway domainStatus object, then retry custom-domain certificate issuance only when Railway reports certificateRetryable=true. A non-retryable result fails without mutation and includes status evidence.

Restore a previous Railway deployment's Docker image and custom variables as the active deployment without rebuilding. Railway must report canRollback=true; the operation requires confirm=true.

Search one cursor-controlled page of Railway templates by text, verification state, and category.

Create all resources from a complete Railway template configuration in a new project or an existing project environment, but leave the resulting changes staged. This does not commit the staged changes or start deployments; commit them separately when ready.

Stop a currently running Railway deployment without deleting the service or its deployment-history record. Requires confirm=true.

Update the hostname or target port of one generated Railway domain, or update the target port of one custom domain.

Update project settings and configuration on Railway. Use this action when you need to modify project properties such as description, visibility settings, or PR deploy preferences. The following fields can be updated: - description: A brief description of the project - isPublic: Whether the project is publicly visible - prDeploys: Whether pull request preview deployments are enabled This is an idempotent operation — updating a project with the same settings multiple times will not change the result after the first update.

Update a service's name or icon without changing environment-specific deployment settings.

Update build/deploy settings for a service in a specific environment on Railway. Use this action when you need to modify service configuration including commands, healthcheck, replicas, region, and cron schedule. This is an idempotent operation. The following fields can be updated: - startCommand: Custom start command for the service - buildCommand: Custom build command - rootDirectory: Root directory for monorepo setups - healthcheckPath: Health check endpoint path - healthcheckTimeout: Health check timeout in seconds - region: Deployment region - numReplicas: Number of service replicas - restartPolicyType: Restart policy (ON_FAILURE, ALWAYS, NEVER) - restartPolicyMaxRetries: Maximum restart retries - cronSchedule: Cron expression for scheduled deployments - sleepApplication: Enable/disable sleep when idle - dockerfilePath: Custom Dockerfile path - watchPatterns: File patterns for automatic redeployment

Rename a Railway volume without changing any volume instance.

Update a Railway volume's environment-specific mount path, attached service, or state. service_id is required on every call as the current or target attachment; set it to null only to explicitly keep or make the instance disconnected.

Create or update a non-empty map of Railway shared-environment or service variables without deleting variables omitted from the submitted map. Railway skips deployments by default. Set skip_deploys=false and confirm_deploys=true to explicitly trigger deployments.