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.
ActionTry it
Integrate Railway MCP
with your AI CRM
Create, inspect, deploy, and manage Railway projects, services, environments, variables, and deployments through Railway's hosted MCP server.
Explore Triggers and Actions
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 the deploy. Before calling this tool you MUST have a GitHub repo to deploy. If the user has not provided one, do not guess — first ask them which GitHub repo to deploy (in 'owner/name' form). If they don't have a repo yet, offer to help create one: if you have tools available to create a GitHub repository (e.g. a GitHub MCP server or `gh` CLI), offer to scaffold and push one for them; otherwise point them to create a repo on GitHub and share its 'owner/name'. Only call this tool once a concrete repo has been confirmed.
ActionTry it
Create-project
Create a new Railway project
ActionTry it
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 instead.
ActionTry it
Delete-feature-flag
Delete a project-scoped feature flag. Workspace-scoped flags cannot be deleted from project context.
ActionTry it
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.
ActionTry it
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 domain you own and returns the DNS records the user must create for it to verify. If environmentId is omitted, the production environment is used.
ActionTry it
Get-feature-flag
Get a Railway feature flag (Signal) by name for a project or its parent workspace scope.
ActionTry it
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` to choose which streams to return (default: ['deploy']).
ActionTry it
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 listed but values are not included — use list-variables for values. If environmentId is omitted, the production environment is used.
ActionTry it
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, the production environment is used.
ActionTry it
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 environmentId is omitted, the project's `production` environment is used when present, otherwise the oldest environment.
ActionTry it
List-deployments
List recent deployments for a Railway project, optionally filtered by environment, service, or status. Returns the most recent first.
ActionTry it
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.
ActionTry it
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.
ActionTry it
List-projects
List all Railway projects accessible to the authenticated user
ActionTry it
List-services
List all services and environments in a Railway project
ActionTry it
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 secrets. Connected OAuth apps receive variable names only. If environmentId is omitted, the production environment is used.
ActionTry it
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.
ActionTry it
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.
ActionTry it
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 are unsure. This does NOT give a service its first deployment: if it has never deployed, nothing here can deploy it, and create-deployment would build a separate new service from a GitHub repo rather than deploying this one.
ActionTry it
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.
ActionTry it
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.
ActionTry it
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 like ${{Postgres.DATABASE_URL}} is supported. Affected services are redeployed unless skipDeploys is true.
ActionTry it
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 are changed. Changes apply on the service's next deployment (use redeploy to apply immediately). Scaling (replicas/regions) and source changes are not handled by this tool.
ActionTry it
Whoami
Get the current authenticated Railway user's profile information
ActionTry it
How the Railway MCP integration works
The Railway MCP integration connects your Dench AI CRM directly to Railway MCP, so agents can read and act on your Railway MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
26 actions are available for agents to invoke on your behalf. Every call runs through Railway MCP's own authorization, scoped to the account you connect.
Set up Railway MCP in Dench
- 1
Sign in to your Dench workspace and open Integrations.
- 2
Find Railway MCP and click Connect — you'll authorize access through Railway MCP's own sign-in flow. No API keys or code required.
- 3
Ask an agent to use Railway MCP in chat, or call it from an automation.
- 4
Manage or disconnect the connection any time from workspace settings.
Frequently asked questions
How does the Railway MCP integration work with Dench?
The Dench Railway MCP integration connects your AI CRM to Railway MCP, so AI agents can work with your Railway MCP data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
What actions can AI agents perform with Railway MCP via Dench?
The Railway MCP integration currently exposes 26 actions, including Accept-deploy, Create-deployment, Create-project, Create-service, Delete-feature-flag, and Fetch-docs. Agents invoke them on your behalf from chat or from automations.
Do I need to write code to connect Railway MCP to Dench?
No. You connect Railway MCP from your Dench workspace using Railway MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Is the Railway MCP integration secure?
Connections are authorized through Railway MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Railway MCP connection from your workspace settings at any time.