Head to head · Cloud hosting · October 2026 research run

InfrOS MCP Server vs Railway MCP Server

Railway MCP Server scores 55.7 (C) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category. Both do cloud hosting.

Best cloud infrastructure tools for AI agents · All 39 infra comparisons

Which one, for what

InfrOS MCP Server F

Best for Cloud architects who want an assistant to draft and compare multi-cloud designs and Terraform.

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Railway MCP Server loses 7 points for them

Watch for

No public tool list, schemas or changelog. The endpoint requires OAuth before initialize

Railway MCP Server C

Best for Agents that deploy and operate applications on Railway from an editor and are content to hand multi-step work to Railway's own agent.

Ahead on

  • Reliability, 57 against 10
  • Schema & documentation, 56 against 15
  • Agent ergonomics, 59 against 21
  • Security & auth, 65 against 49
  • Payments & pricing, 60 against 40
  • Maintenance & community, 83 against 35
  • Transparency & trust, 74 against 26

Also in its favour

  • Runs on your own machine

Watch for

The hosted server's source and tool schemas are not public, so inputs can only be read after signing in.

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Railway MCP Server +48

InfrOS MCP Server 35

Read as a closed hosted service. The MCP server was announced on 5 November 2026, 13 days before the check (30). No changelog. The news page lists dated launches on 30 September and 9 November 2026, two in 90 days (0). Support by email and a Slack chat link, with no public changelog (5). Not in the official MCP registry, by a search for infros (0). No SDK (0). 30 + 0 + 5 + 0 + 0 = 35.

Railway MCP Server 83

The Railway CLI, which carries the proxy, tagged v5.71.0 on 19 October 2026 (16 days, 30). 113 CLI tags from 6 August to 4 November 2026 in the repository (20). GitHub's pages and API answer 403 to us, so issue handling was not re-read. The clone shows pull requests merged into the main branch up to #1300 on 16 October, and Railway runs a feedback thread for the server on Central Station (10 of 25). The official MCP registry listed com.railway/mcp as active under the vendor's domain namespace per the 9 October check, not re-read on 4 November (15). The CLI's CI runs cargo check, clippy, a cross build and cargo test on pushes to master and pull requests, beside a cargo-audit workflow and a lockfile. Workflow results were not seen (8 of 10). 30 + 20 + 10 + 15 + 8 = 83.

Transparency & trust Railway MCP Server +48

InfrOS MCP Server 26

Closed service. The published terms cover only the website, and the product is under separate agreements that aren't public (5). The privacy policy covers website forms only, with no product data, retention or DPA found (5). No deprecation policy (0). No subprocessors or data locations disclosed (0). 5 + 5 + 0 + 0 = 10.

Railway MCP Server 74

The hosted server is closed source under clear terms. The CLI proxy and the local server are MIT (20 of 30). The DPA is published in full. The privacy policy's full text was not read. Audit log and image retention are stated by plan, and nothing was found on what the hosted server or railway-agent keeps from a session (18 of 30). The old npm server was deprecated on 23 May 2026 with a shim and a registry notice, and API fields are marked @deprecated before removal with no stated period. The terms let Railway suspend or discontinue any part of the Services (10 of 20). The DPA names Google Cloud Platform and the United States, promises ten days' notice of a new sub-processor and points to a list at trust.railway.com that was not read (13 of 20). Per the 9 October check, not re-read on 4 November (Railway's terms bar scraping its pages). The CLI's telemetry is on by default and documented with an opt-out (railway telemetry disable, DO_NOT_TRACK or RAILWAY_NO_TELEMETRY); the source sends events with the account token, the linked project, environment and service IDs and a caller name read from the process tree. That is scored on the local-software reading, not on this hosted line.

Reliability Railway MCP Server +47

InfrOS MCP Server 10

Graded as a hosted MCP server. No status page found (0). No history to read (5). No rate limits published (0). No 429, retry or backoff guidance (0). No SLA, and Enterprise lists dedicated support without a figure (0). InfrOS's own pages don't call the server beta, but the press article on its news page calls it a preview, so half (5). 0 + 5 + 0 + 0 + 0 + 5 = 10.

Railway MCP Server 57

Scored as a hosted server. Railway's terms bar crawling or scraping any page of its websites by manual or automated means, so no railway.com page was re-read on 4 November and the status lines are per the 9 October check. status.railway.com is an in-house status page with component history by region and for the API and OAuth login (20). On 9 October it listed about 25 incidents from 11 July to 8 October 2026, most on slow builds and deployments, including a five-minute routing failure for all domains on 30 September, services and databases unavailable for some users in US West on 3 October and a hardware fault in US West on 29 August. The MCP server is not a component. The readable part of today's window (6 August to 8 October) holds one major, the all-domain routing failure, and 9 October to 4 November was not read (10 of 30). No limit is stated for the MCP server. The public API's limits are published with numbers, 100 to 10,000 requests an hour by plan (8 of 15, held partial). The API docs give Retry-After on 429, backoff advice and retry rules for mutations, with no idempotency key, which this run reads as safe-retry guidance without keys (12 of 15, was 10). A 99.99% SLA is named for Enterprise with terms by contract, and no SLA document was found or read (0 of 10, was 5). The docs carried no beta label, but the April 2026 launch note called it ready for public testing (7 of 10, held partial). 20 + 10 + 8 + 12 + 0 + 7 = 57.

Schema & documentation Railway MCP Server +41

InfrOS MCP Server 15

No tool list or schema is published, and the endpoint needs OAuth before initialize. An OAuth protected-resource document states the scopes and bearer method (5 of 25). llms.txt exists but holds crawler rules and brand notes, not docs (2). The setup post describes four permission groups and what each allows, not individual tools (5). Inputs unknown (0). One example prompt and no documented errors (3). No versioning or changelog found (0). 5 + 2 + 5 + 0 + 3 + 0 = 15.

Railway MCP Server 56

The hosted server's source is closed and tools/list needs a signed-in client, so no tool schema was read. A server card and a registry entry are public, and the CLI proxy source shows that tools declare their parameters (15 of 25). llms.txt on both sites and a Markdown twin of every docs page (10). The docs name the 11 tools and describe four of them in a line each. The descriptions the server sends were not read (8 of 20). Input types, enums and bounds could not be read (5 of 15). The docs give example prompts and the 401 challenge, and the API docs list error codes. No list of tool errors was found (9 of 15). Railway's changelog is weekly and dated, but the growth from seven tools to 11 has no dated entry found, and the hosted server shows a fixed version 1.0.0 (9 of 15).

Agent ergonomics Railway MCP Server +38

InfrOS MCP Server 21

Tool count and sizes couldn't be read. Scope-based access may narrow what a session can do, so partial credit (8). No pagination or output controls documented (0). Errors undocumented beyond the 401 with a WWW-Authenticate header (2). The setup post says the assistant states the credit price and waits for a yes, but no annotations or idempotency are documented (6). One URL and an OAuth sign-in, with no SDK (5). 8 + 0 + 2 + 6 + 5 = 21.

Railway MCP Server 59

Eleven tools, one over the ten that earns full marks, with railway-agent taking multi-step work in a single call (20 of 25). The three list tools are the only read tools apart from the flag tools. Pagination and size controls could not be read (6 of 20). A missing or expired token answers 401 with a WWW-Authenticate challenge, the CLI proxy returns a login hint, and API errors carry a code and a trace id (12 of 20). The docs say destructive tools are marked at the protocol level so clients prompt. Read-only hints were not established, and there is no idempotency key (12 of 20). The CLI proxy fills project context from the linked directory for tools that accept it. Two official SDKs for the platform API were not found (9 of 15).

Payments & pricing Railway MCP Server +20

InfrOS MCP Server 40

No payment protocol (0). Credit costs per action are public, but no price per credit or pack is, so the money price is hidden, as for Datadog's plan-only case (10). A free trial of 700 credits with no card (30). A person signs up in a browser and approves OAuth (0). 0 + 10 + 30 + 0 = 40.

Railway MCP Server 60

No x402, MPP or L402 on the server (0). Railway can be provisioned through Stripe's Agentic Provisioning Protocol, which is a separate route and earns nothing here. Plan fees and per-second prices for CPU, memory, volumes and egress are public (20). The trial gives $5 of credit for 30 days with no card, followed by a Free plan with $1 a month (20). Dynamic client registration needs no setup, but a person has to sign in and approve the grant in a browser or with a device code (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Score by category

CategoryWeightInfrOS MCP ServerRailway MCP ServerEdge
Reliability16%1057Railway MCP Server +47
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%1556Railway MCP Server +41
Agent ergonomics13%2159Railway MCP Server +38
Security & auth14%4965Railway MCP Server +16
Payments & pricing10%4060Railway MCP Server +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3583Railway MCP Server +48
Transparency & trust7%2674Railway MCP Server +48
Negative events≤150-7
TotalF 26.8/100C 55.7/100

Facts side by side

FactInfrOS MCP ServerRailway MCP Server
KindMCP serverMCP server
VendorInfrOSRailway Corporation
Hosted endpointhttps://api.app.infros.io/assistant/mcphttps://mcp.railway.com
TransportsStreamable HTTPStreamable HTTP, stdio
AuthOAuthOAuth
PricingPay per useYour plan
x402nono
LicencenoneProprietary hosted server under Railway's Terms of Service. The Railway CLI, which carries the stdio proxy and a separate local MCP server, is MIT
Tools exposednone11
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.railway/mcp
Last release2026-11-052026-10-19
Terms last updatedno document linkedcouldn't be read
Privacy policy last updatedno document linkedcouldn't be read
Customer content may train modelsnot read yetcouldn't be read
Terms restrict automated accessnot read yetcouldn't be read
Terms restrict benchmarkingnot read yetcouldn't be read
Terms or service can change without noticenot read yetcouldn't be read
Arbitration or class-action waivernot read yetcouldn't be read
Popularitynone426k npm/wk

How the scores have moved

Verdicts

InfrOS MCP Server

Agents reach InfrOS through a remote MCP server with OAuth scopes that separate reading, writing, spending credits and administration, and a free trial of 700 credits needs no card. The tool list, rate limits, status, changelog and product terms aren't public, and the money price of a credit isn't published.

Railway MCP Server

A small hosted server with 11 tools, OAuth grants limited to chosen workspaces and one-hour tokens. Most infrastructure work goes through the railway-agent tool, which is billed by model tokens. The hosted server's source and tool schemas are not public, there is no read-only scope, and the CLI fixed a database password exposure in September without an advisory.

Before you call either

InfrOS MCP Server

  1. Ask for the infros:read and infros:write scopes only, unless the person wants design runs started. infros:spend uses the organisation's credits
  2. Tell the person the credit price and wait for a yes before a design run or a Terraform export
  3. If the endpoint returns 401, run the client's MCP sign-in again. For Codex, run codex mcp login infros
  4. Show the person generated Terraform before anyone applies it to a live cloud account

Railway MCP Server

  1. Connect to https://mcp.railway.com with OAuth, or run railway mcp after railway login. Project tokens are refused.
  2. Treat redeploy, accept-deploy, delete-feature-flag and railway-agent as actions that change production. Confirm the project and environment first.
  3. railway-agent spends model tokens billed to the workspace. Use the single-purpose tools for listing and redeploying.
  4. For variables, domains, volumes, logs or metrics as separate tools, use railway mcp local, which has a different tool set.
  5. On a 401, follow the WWW-Authenticate challenge and run the OAuth flow again. Access tokens expire after one hour.

Questions

Which is better for AI agents, InfrOS MCP Server or Railway MCP Server?

Railway MCP Server scores 55.7 (C) on agent readiness against InfrOS MCP Server's 26.8 (F), and leads in every scored category.

Do InfrOS MCP Server and Railway MCP Server need an API key?

Both use an OAuth sign-in.

Can an agent call InfrOS MCP Server and Railway MCP Server without installing anything?

Yes. InfrOS MCP Server has a hosted endpoint at https://api.app.infros.io/assistant/mcp and Railway MCP Server at https://mcp.railway.com.

Other comparisons with InfrOS MCP Server or Railway MCP Server

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.