Railway

40/100
Last tested 2026-11-10 (Fresh: tested within 30 days) Failed Deprecated Key unknown

No advisories in range for tested 0.1.12 (checked 2026-11-09)

Security review: not tested

Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology

  • Install20/20
  • Handshake0/30
  • Maintenance0/25
  • Docs10/15
  • License10/10

@railway/mcp-server 0.1.12 is a deprecated compatibility shim: npm marks it "Deprecated: Railway MCP is now bundled into the Railway CLI. Use 'railway mcp'. See https://docs.railway.com/cli/mcp." and its README says it "is a compatibility shim that launches: railway mcp" (https://registry.npmjs.org/@railway/mcp-server). Railway's docs say the Railway MCP server runs at https://mcp.railway.com (https://docs.railway.com/ai/mcp-server).

Transport (tested 2026-10-22): stdio

Tested version: 0.1.12 · tested 2026-10-22

Token cost (estimate): the figure is pending. We have no tools/list capture to estimate from.

Permissions: the figure is pending.

Score 40/100 · Tools 0 · Token cost pending · Compare · Last tested 2026-11-10 · Version tested 0.1.12 · Package @railway/mcp-server · Repo railwayapp/railway-mcp-server

Summary: Railway requires credentials or a backing service before it will list tools; it is deprecated or archived, so prefer a maintained alternative.

Evidence summary

Handshake
fail
Tools listed
0
Context cost
Pending The token cost figure is pending. ranking
API key
Key: unknown
Tested
2026-11-10

Test results

TestResultPointsEvidence
installpass20npm install @railway/mcp-server (Node 20, Linux) succeeded in 0s.
handshakefail0Server did not complete the handshake without credentials or a backing service (tall Or run the local stdio server directly with: railway mcp Docs: https://docs.railway.com/cli/mcp exited code 1).
maintenancefail0Deprecated on npm: Deprecated: Railway MCP is now bundled into the Railway CLI. Use 'railway mcp'. See https://docs.railway.com/cli/mcp.; GitHub repo railwayapp/railway-mcp-server is archived.
docspartial10install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package).
licensepass10MIT (OSI-approved).

Local-model readiness

Not tested

Not yet tested (no tools/list response without credentials).

What we tested and what we didn't

Tested on 2026-11-10

  • Install from the registry
  • We attempted an MCP initialize with no credentials; it did not complete, so we never reached the tool list (Method details: initialize failed; tools/list not sent)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Checked on 2026-11-09 for version 0.1.12 against OSV, GitHub advisories, GitHub repository advisories. Scope: the package itself; dependencies not scanned.

No published advisories found in OSV and GitHub advisories for @railway/mcp-server 0.1.12 as of 2026-11-09. This is not a security audit.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

No tool list: this server did not list tools without credentials in our test, so tool changes are not tracked.

Raw test record (JSON)
{
  "name": "@railway/mcp-server",
  "version": "0.1.12",
  "registry": "npm",
  "status": "failed",
  "tested": "2026-11-10",
  "tools_count": null,
  "deprecated": true,
  "archived": true,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install @railway/mcp-server` (Node 20, Linux) succeeded in 0s."
    ],
    "handshake": [
      "fail",
      0,
      "Server did not complete the handshake without credentials or a backing service (tall\n\nOr run the local stdio server directly with:\n  railway mcp\n\nDocs: https://docs.railway.com/cli/mcp\n\n\nexited code 1)."
    ],
    "maintenance": [
      "fail",
      0,
      "Deprecated on npm: Deprecated: Railway MCP is now bundled into the Railway CLI. Use 'railway mcp'. See https://docs.railway.com/cli/mcp.; GitHub repo railwayapp/railway-mcp-server is archived."
    ],
    "docs": [
      "partial",
      10,
      "install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  }
}

Install

npx -y @railway/mcp-server

Pin the version we tested

npx -y @railway/mcp-server@0.1.12

tested 2026-11-10. Newer versions may differ and were not tested by us.

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

Tools listed

Not available (handshake did not complete without credentials).

Quick config

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

Test history

Follow this server (RSS) · Monthly changelog

Related: Best cloud MCP servers · Fix: MCP error -32000 Connection closed

FAQ

Is Railway deprecated?

Yes. @railway/mcp-server is deprecated on npm and its GitHub repo is archived (as of 2026-10-22). npm says: "Deprecated: Railway MCP is now bundled into the Railway CLI. Use 'railway mcp'. See https://docs.railway.com/cli/mcp."

What replaces Railway?

None identified. We have no evidence of a maintained replacement yet.

Does Railway need an API key?

Unknown. It did not complete the handshake in our test without credentials or a backing service, and gave no clear credential message.

Embed the badge

TestedMCP: 40/100, tested 2026-11-10

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue