Connect Railway MCP to your AI agent
Create, inspect, deploy, and manage Railway projects, services, environments, variables, and deployments through Railway's hosted MCP server.
We set up the connection using your own Railway MCP account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.
Actions
What your agent can do in Railway MCP
Each one is a real action the agent can take on its own, the same things a person clicking around Railway MCP could do. Read-only by default; write actions are confirmed against your policy.
- Accept deploy DESTRUCTIVE: Commits all staged changes in a Railway environment and triggers a deploy. Only use this when the user has explicitly confirmed they want to deploy.
- Create deployment Create a new service from a GitHub repository and trigger its first deployment. The repo must be one the authenticated user has connected via GitHub. Returns the new service; use get-status or list-deployments to follow…
- Create project Create a new Railway project
- Create service Create a new service in a project from a Docker image, or an empty service to configure later (e.g. before setting variables and attaching a source). To create a service from a GitHub repository, use create-deployment i…
- Delete feature flag Delete a project-scoped feature flag. Workspace-scoped flags cannot be deleted from project context.
- Fetch docs Fetch the full markdown content of a Railway documentation page by URL or slug (e.g. 'https://docs.railway.com/quick-start' or 'reference/variables'). Use search-docs first to find the right page.
- Generate domain Expose a service publicly. Without `domain`, generates a Railway *.up.railway.app service domain (if the service already has domains, they are returned instead of creating another). With `domain`, attaches a custom doma…
- Get feature flag Get a Railway feature flag (Signal) by name for a project or its parent workspace scope.
- Get logs Get logs from Railway for a deployment — covers deploy (runtime), build, and http (proxy request) contexts. Pass a specific deploymentId, or pass serviceId + environmentId to resolve the latest deployment. Use `types` t…
- Get service config Get a service's configuration in an environment: source (repo/image), build settings, deploy settings (start command, healthcheck, replicas, cron, restart policy), networking, and volume mounts. Variable names are liste…
- Get service metrics Get resource usage metrics (CPU, memory, disk, network) for a service, summarized as current/average/min/max over a time window. Defaults to CPU_USAGE and MEMORY_USAGE_GB over the last hour. If environmentId is omitted,…
- Get status Get the deployment status of a Railway project environment. Returns project + environment metadata and, for each service in the environment, its latest deployment status, replica count, and cron schedule. If environment…
- List deployments List recent deployments for a Railway project, optionally filtered by environment, service, or status. Returns the most recent first.
- List domains List all domains (Railway-generated service domains and custom domains) for a service in an environment. If environmentId is omitted, the production environment is used.
- List feature flags List Railway feature flags (Signals) for a project and optionally the parent workspace. Project flags are editable with admin access; workspace flags are read-only from project context.
- List projects List all Railway projects accessible to the authenticated user
- List services List all services and environments in a Railway project
- List variables List all environment variables for a service, fully rendered (reference variables like ${{Postgres.DATABASE_URL}} are resolved). With a Railway session or API token, values are returned in plaintext and may contain secr…
- List workspaces List the Railway workspaces the current user belongs to. Use a workspace ID with create-project to choose where a project is created.
- Railway agent Send a message to Railway's AI agent for complex infrastructure operations. The agent can inspect services, diagnose issues, and take actions on your behalf.
- Redeploy Re-run the most recent deployment of a service in a given environment, reusing that deployment's existing build. Only works on a service that has already deployed in that environment — check with list-deployments if you…
- Search docs Search the Railway documentation (docs.railway.com) for features, configuration, guides, and tutorials. Returns matching sections with URLs — use fetch-docs to read a full page.
- Set feature flag Create a project-scoped feature flag or update its default value. Use list-feature-flags and get-feature-flag to inspect existing flags first.
- Set variables Set one or more environment variables on a service (or environment-wide shared variables when serviceId is omitted). Existing variables with the same name are overwritten; others are left unchanged. Reference syntax lik…
- Update service 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. Only the fields you pass…
- Whoami Get the current authenticated Railway user's profile information
Setup
How we connect it
- 1
Connect your account
You log in with your own Railway MCP account. We never see your password, and you can revoke access from Railway MCP at any time.
- 2
Set the guardrails
Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.
- 3
We keep it running
Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.
FAQ
Railway MCP questions, answered.
You sign in with your own Railway MCP account. Permissions are scoped to the minimum the agent needs, the connection is health-checked, and you can revoke access from Railway MCP at any time.
The actions Railway MCP's API allows, the same things a person clicking around the app could do. Connections start read-only by default; write actions are confirmed against the policy you set before the agent takes them.
Connections are priced per tool on top of the base plan. Some are included, some are premium. See pricing for how connection charges work.
Standard tools are ready inside 7 business days of the setup call. We test the connection end to end, walk you through how the agent uses it, and watch the first week of activity.
Ready to put Railway MCP to work?
Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.
All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by Railway MCP.