How to integrate Railway MCP with Atomic Agent

DESTRUCTIVE: Commits all staged changes in a Railway environment and triggers a deploy.

Attach a source to an existing service: a GitHub repository (deploys on push, builds immediately) or a Docker image.

Create an S3-compatible object storage bucket in a project and provision it in an environment.

Create a new service from a GitHub repository and trigger its first deployment.

Create a new Railway project

Create a new service in a project from a Docker image, or an empty service to configure later (e.

Expose a service on the public internet over a raw TCP port (e.

Create a persistent volume in a project and optionally attach it to a service at a mount path.

Permanently delete an object storage bucket and its contents.

Delete a project-scoped feature flag.

Permanently delete a service: its deployments stop and are removed, along with its domains, variables and deployment triggers.

Remove a service's TCP proxy, taking its public endpoint offline.

Permanently delete a volume and its data.

Inventory of everything in a Railway environment — services, volumes, buckets, shared variable names — with staged changes applied.

Everything about one service in an environment: its config with staged changes applied (source, build, deploy, networking, volume mounts), the per-field staged changes pending on it, mounted volumes, live domains and TCP proxies, and the latest deployment.

Get detailed status for one domain on a service, by hostname, URL, or domain ID: required DNS records and whether they currently match, ownership verification, certificate status, and any certificate error.

Health overview of every service in an environment in one call: current LIVE (settled) deployment state, replica status, recent failures, unresolved warnings/criticals, and cron execution results.

Fetch the full markdown content of a Railway documentation page by URL or slug (e.

Expose a service publicly.

Get the AI-generated diagnosis for a failed deployment: root cause category, analysis, and suggested fixes, along with deployment context (service config, source repo, branch, commit, PR, failure stage and error).

Get a Railway feature flag (Signal) by name for a project or its parent workspace scope.

Get logs from Railway for a deployment — covers deploy (runtime), build, and http (proxy request) contexts.

Prefer describe-service: it applies the staged diff onto the live config for you and adds mounted volumes, domains, TCP proxies and the latest deployment.

Get resource usage metrics (CPU, memory, disk, network) for a service, summarized as current/average/min/max over a time window.

Show the changes staged in a Railway environment that accept-deploy would commit: per resource (service, volume, bucket, group) the action — create, delete, update — and each changed field with its live and staged value.

Prefer describe-environment: it also lists services that exist only in the staged patch, unattached volumes, and each resource's staged state.

Get the HTTP error rate for a service over time — the share of requests answered with a 5xx.

Get HTTP request counts for a service, bucketed over time and split by response status class (2xx/3xx/4xx/5xx).

Get HTTP latency percentiles (p50, p90, p95, p99) for a service, bucketed over time, in milliseconds.

List recent deployments for a Railway project, optionally filtered by environment, service, or status.

List all domains (Railway-generated service domains and custom domains) for a service in an environment.

List Railway feature flags (Signals) for a project and optionally the parent workspace.

List all Railway projects accessible to the authenticated user

List the ids and names of all services and environments in a Railway project.

List the TCP proxies exposing a service over the public internet on a raw TCP port (e.

List all environment variables for a service, fully rendered (reference variables like ${{Postgres.

List the Railway workspaces the current user belongs to.

Send a message to Railway's AI agent for complex infrastructure operations.

Re-run the most recent deployment of a service in a given environment, reusing that deployment's existing build.

Restart a service's running deployment in place — the containers restart without rebuilding the image, and no new deployment is created (use redeploy for a fresh build copy).

Search the Railway documentation (docs.

Create a project-scoped feature flag or update its default value.

Set one or more environment variables on a service (or environment-wide shared variables when serviceId is omitted).

Update a service's configuration: build/start/pre-deploy commands, healthcheck, sleep mode, root directory, cron schedule, Dockerfile path, restart policy, config file path, and watch patterns.

Update a volume's name and/or mount path.

Get the current authenticated Railway user's profile information