Railway MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check-railway-statusA | Check whether the Railway CLI is installed and if the user is logged in. This tool helps agents verify the Railway CLI setup before attempting to use other Railway tools. |
| create-environmentB | Create a new Railway environment for the currently linked project. Optionally duplicate an existing environment and set service variables. |
| create-project-and-linkC | Create a new Railway project and link it to the current directory |
| deploy-templateA | Search and deploy Railway templates. This tool will search for templates using fuzzy search and automatically deploy the selected template to the current Railway project and environment. |
| deployC | Upload and deploy from the current directory. Supports CI mode, environment, and service options. |
| generate-domainB | Generate a domain for the currently linked Railway project. If a domain already exists, it will return the existing domain URL. Optionally specify a service to generate the domain for. |
| get-logsA | Get build or deployment logs for the currently linked Railway project. This will only pull the latest successful deployment by default, so if you need to inspect a failed build, you'll need to supply a deployment ID. You can optionally specify a deployment ID, service, and environment. If no deployment ID is provided, it will get logs from the latest deployment. The 'lines' and 'filter' parameters require Railway CLI v4.9.0+. Use 'lines' to limit the number of log lines (disables streaming) and 'filter' to search logs by terms or attributes (e.g., '@level:error', 'user', '@level:warn AND rate limit'). For older CLI versions, these parameters will be ignored and logs will stream. |
| link-environmentB | Link to a specific Railway environment. If no environment is specified, it will list available environments for selection. |
| link-serviceB | Link a service to the current Railway project. If no service is specified, it will list available services |
| list-deploymentsA | List deployments for a Railway service with IDs, statuses and other metadata. Requires Railway CLI v4.10.0+. |
| list-projectsB | List all Railway projects for the currently logged in account |
| list-servicesC | List all services for the currently linked Railway project |
| list-variablesC | Show variables for the active environment |
| set-variablesC | Set environment variables for the active environment |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools have distinct purposes targeting specific Railway resources like projects, environments, services, deployments, and variables, with clear action verbs. However, 'deploy' and 'deploy-template' could be confused as both handle deployment, though their descriptions clarify one is for directory uploads and the other for templates.
Tool names predominantly follow a consistent verb-noun pattern (e.g., create-environment, list-services, set-variables), with clear and readable conventions. Minor deviations include 'check-railway-status' using a verb-noun-adjective structure and hyphenated names throughout, but overall consistency is high.
With 14 tools, the count is well-scoped for managing Railway projects, covering setup, deployment, logging, and resource management. Each tool serves a clear purpose without redundancy, fitting typical server tool ranges and the domain's complexity.
The tool set provides comprehensive coverage for Railway operations, including project and environment creation, deployment, logging, variable management, and listing resources. There are no obvious gaps; agents can perform full lifecycle management from setup to monitoring.