# io.github.railwayapp/mcp-server (npm · @railway/mcp-server)

Official Railway MCP server

- Trust score: 79/100 (medium)
- Change this week: +33
- Registry status: deprecated
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

> **Deprecated**: this server is marked deprecated in the MCP registry.

## Components

- npm · `@railway/mcp-server`: 79/100 (this document), [markdown](https://verifymcp.io/servers/railwayapp-mcp-server/railway-mcp-server.md), [page](https://verifymcp.io/servers/railwayapp-mcp-server/railway-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@railway/mcp-server`
- Version: `0.1.11`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (99 of 103), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to railwayapp/railway-mcp-server).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 73 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1387 tokens (~99/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add railwayapp-mcp-server -- npx -y @railway/mcp-server
```

### Codex

```bash
codex mcp add railwayapp-mcp-server -- npx -y @railway/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "railwayapp-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@railway/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add railwayapp-mcp-server --command npx --arg -y --arg @railway/mcp-server
```

### Hermes

```yaml
mcp_servers:
  railwayapp-mcp-server:
    command: "npx"
    args: ["-y", "@railway/mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "railwayapp-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@railway/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-04 (score 79, 0)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail

### 2026-08-02 (score 79, +58)

- [security improvement] Provenance: unverified → pass
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] The attested source repository moved: railwayapp/railway-mcp-server
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: MIT

### 2026-07-31 (score 21, −25)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 46, +21)

- [functional regression] Dependency health: partial → unverified
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: unverified
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 98
- [functional] First check of Schema quality: pass

### 2026-07-27 (score 25)

First indexed and scored.

## MCP tools (14)

### `check-railway-status` (~43 tokens)

Check Railway CLI Status

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-environment` (~102 tokens)

Create Environment

Create a new Railway environment for the currently linked project. Optionally duplicate an existing environment and set service variables.

Input parameters:

- `duplicateEnvironment` (string): The name of an existing environment to duplicate
- `environmentName` (string, required): The name for the new environment
- `serviceVariables` (array): Service variables to assign in the new environment (only works when duplicating)
- `workspacePath` (string, required): The path to the workspace where the environment should be created

### `create-project-and-link` (~49 tokens)

Create Railway Project

Create a new Railway project and link it to the current directory

Input parameters:

- `projectName` (string, required)
- `workspacePath` (string, required): The path to the workspace to create the project in

### `deploy-template` (~110 tokens)

Deploy Railway Template

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.

Input parameters:

- `searchQuery` (string, required): Search query to filter templates by name, description, or category
- `teamId` (string): The ID of the team (optional)
- `templateIndex` (number): Index of the template to deploy (required if multiple templates found)
- `workspacePath` (string, required): The path to the workspace to deploy the template to

### `deploy` (~94 tokens)

Deploy to Railway

Upload and deploy from the current directory. Supports CI mode, environment, and service options.

Input parameters:

- `ci` (boolean): Stream build logs only, then exit (equivalent to setting $CI=true)
- `environment` (string): Environment to deploy to (defaults to linked environment)
- `service` (string): Service to deploy to (defaults to linked service)
- `workspacePath` (string, required): The path to the workspace to deploy

### `generate-domain` (~79 tokens)

Generate Railway Domain

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.

Input parameters:

- `service` (string): The name of the service to generate the domain for (optional)
- `workspacePath` (string, required): The path to the workspace to generate domain for

### `get-logs` (~400 tokens)

Get Railway Logs

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.

Input parameters:

- `deploymentId` (string): Deployment ID to pull logs from. Omit to pull from latest deployment
- `environment` (string): Environment to view logs from (defaults to linked environment)
- `filter` (string): Filter logs by search terms or attributes. Requires Railway CLI v4.9.0+. Examples: 'error', '@level:error', '@level:warn AND rate limit', 'user login', '@status:500'. See https://docs.railway.com/gui…
- `json` (boolean): JSON provides structured log data with more information (e.g. timestamps) but uses more tokens. Defaults to false to save tokens. Set to true for more detailed logs.
- `lines` (number): Number of log lines to return (disables streaming). Requires Railway CLI v4.9.0+. Useful for searching through recent logs.
- `logType` (string, required): Type of logs to retrieve: 'build' for build logs or 'deploy' for deployment logs
- `service` (string): Service to view logs from (defaults to linked service)
- `workspacePath` (string, required): The path to the workspace to get logs from

### `link-environment` (~62 tokens)

Link Environment

Link to a specific Railway environment. If no environment is specified, it will list available environments for selection.

Input parameters:

- `environmentName` (string, required): The environment name to link to
- `workspacePath` (string, required): The path to the workspace to link the environment to

### `link-service` (~60 tokens)

Link Railway Service

Link a service to the current Railway project. If no service is specified, it will list available services

Input parameters:

- `serviceName` (string): The service name to link
- `workspacePath` (string, required): The path to the workspace to link the service to

### `list-deployments` (~141 tokens)

List Railway Deployments

List deployments for a Railway service with IDs, statuses and other metadata. Requires Railway CLI v4.10.0+.

Input parameters:

- `environment` (string): Environment to list deployments from (defaults to linked environment)
- `json` (boolean): Return deployments as structured JSON data. When true, the output will contain ids, statuses, and other metadata
- `limit` (number): Maximum number of deployments to show (default: 20, max: 1000)
- `service` (string): Service name or ID to list deployments for (defaults to linked service)
- `workspacePath` (string, required): The path to the workspace to list deployments from

### `list-projects` (~20 tokens)

List Railway Projects

List all Railway projects for the currently logged in account

### `list-services` (~35 tokens)

List Railway Services

List all services for the currently linked Railway project

Input parameters:

- `workspacePath` (string, required): The path to the workspace to list services from

### `list-variables` (~90 tokens)

List Railway Variables

Show variables for the active environment

Input parameters:

- `environment` (string): The environment to show variables for (optional)
- `json` (boolean): Output in JSON format (optional)
- `kv` (boolean): Show variables in KV format (optional)
- `service` (string): The service to show variables for (optional)
- `workspacePath` (string, required): The path to the workspace to list variables from

### `set-variables` (~102 tokens)

Set Railway Variables

Set environment variables for the active environment

Input parameters:

- `environment` (string): The environment to set variables for (optional)
- `service` (string): The service to set variables for (optional)
- `skipDeploys` (boolean): Skip triggering deploys when setting variables (optional)
- `variables` (array, required): Array of '{key}={value}' environment variable pairs to set
- `workspacePath` (string, required): The path to the workspace to set variables in

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/railwayapp-mcp-server/railway-mcp-server#diagnostics

## Score history

- 2026-08-04: 79
- 2026-08-03: 79
- 2026-08-02: 79
- 2026-08-01: 21
- 2026-07-31: 21
- 2026-07-30: 46
- 2026-07-28: 46
- 2026-07-27: 25

## Links

- npm package: https://www.npmjs.com/package/@railway/mcp-server
- Socket report: https://socket.dev/npm/package/@railway/mcp-server
- Repository: https://github.com/railwayapp/railway-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/railwayapp-mcp-server/railway-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/railwayapp-mcp-server/railway-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/railwayapp-mcp-server/railway-mcp-server