{
  "data": {
    "a": {
      "slug": "railway-mcp-server",
      "name": "Railway MCP Server",
      "vendor": "Railway Corporation",
      "vendorUrl": "https://railway.com",
      "kind": "mcp",
      "category": "infrastructure",
      "summary": "Railway's official MCP server is hosted at mcp.railway.com. It lets an agent list and create projects, redeploy services, manage feature flags and hand multi-step work to Railway's own agent, through OAuth or the Railway CLI.",
      "url": "https://www.anchorterminal.com/tools/railway-mcp-server",
      "markdownUrl": "https://www.anchorterminal.com/tools/railway-mcp-server.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/railway-mcp-server.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/railway-mcp-server.json",
      "repo": "https://github.com/railwayapp/cli",
      "license": "Proprietary hosted server under Railway's Terms of Service. The Railway CLI, which carries the stdio proxy and a separate local MCP server, is MIT",
      "transports": [
        "streamable-http",
        "stdio"
      ],
      "remoteUrl": "https://mcp.railway.com",
      "packages": [
        {
          "registry": "npm",
          "name": "@railway/cli"
        }
      ],
      "auth": "oauth",
      "authNotes": "OAuth, either handled by the MCP client or reused from a `railway login` session through the CLI. An unauthenticated request answers 401 with a pointer to the protected-resource metadata, which names the authorisation server at backboard.railway.com and one scope, `workspace:member`. The authorisation server supports the authorisation code grant with PKCE (S256), the device code grant, refresh tokens and dynamic client registration. On the consent screen a person picks which workspaces and projects the client reaches. Access tokens last one hour and refresh tokens rotate. Grants are revoked in the dashboard, and there is no revocation endpoint. Project tokens are refused.",
      "pricing": "byo-plan",
      "pricingNotes": "The server itself has no charge. Tools act on a Railway workspace and bill under its plan. A new account gets a 30-day trial with a one-time $5 credit and no card, then the Free plan with $1 of usage a month. Hobby is $5 a month and Pro $20 a month, each with the same amount of usage included, and Enterprise is priced by sales. Usage is metered by the second. The `railway-agent` tool runs Railway's own agent, which is billed for the model tokens it uses at Anthropic's published rates with no markup (checked 2026-10-09).",
      "priceSummary": "Your plan",
      "where": "both",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in the MCP server docs, the CLI docs, llms.txt, auth.md or the pricing file (checked 2026-10-09). Railway can be provisioned through Stripe's Agentic Provisioning Protocol, which is a separate route and not a payment protocol on the MCP endpoint.",
        "endpoints": []
      },
      "toolCount": 11,
      "popularity": {
        "githubStars": null,
        "npmWeekly": 426205,
        "pypiWeekly": null,
        "asOf": "2026-10-09"
      },
      "docsUrl": "https://docs.railway.com/ai/mcp-server",
      "llmsTxt": "https://docs.railway.com/llms.txt",
      "openapi": "https://railway.com/openapi.json",
      "registryName": "com.railway/mcp",
      "capabilities": [
        "infra.cloud",
        "code.deploy",
        "analytics.flags"
      ],
      "tags": [
        "official",
        "hosted",
        "mcp",
        "oauth",
        "llms-txt",
        "openapi",
        "status-page",
        "soc2",
        "free-tier"
      ],
      "lastRelease": "2026-10-08",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 56.7,
        "grade": "C",
        "agentReady": false,
        "rank": 565,
        "ranked": true,
        "rankOf": 842,
        "categoryRank": 6,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 59,
          "maintenance": 83,
          "payments": 40,
          "reliability": 60,
          "schema": 56,
          "security": 65,
          "transparency": 73
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "medium",
          "date": "2026-10-09"
        },
        "negative": -4,
        "negativeNotes": [
          "30 March 2026. A CDN configuration change cached GET responses on about 0.05% of Railway domains for 52 minutes, so pages meant for one user may have been served to another. Railway reverted it, purged the cache and published a report the same day. Fixed and documented, so 4 is deducted (https://blog.railway.com/p/incident-report-march-30-2026-authenticated-user-data-cached)."
        ],
        "verdict": "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 status page lists about 25 incidents in 90 days.",
        "bestFor": "Agents that deploy and operate applications on Railway from an editor and are content to hand multi-step work to Railway's own agent.",
        "strengths": [
          "OAuth with PKCE, dynamic client registration and a device code grant. A person picks the workspaces and projects a client reaches.",
          "Access tokens last one hour, refresh tokens rotate, and the CLI route keeps any long-lived credential out of editor configuration.",
          "Eleven tools keep the context cost low, with `railway-agent` taking multi-step work in one call.",
          "The trial needs no card and prices for CPU, memory, volumes and egress are public and metered by the second.",
          "The CLI that carries the proxy had more than 100 tagged releases in 90 days, the latest on 8 October 2026."
        ],
        "weaknesses": [
          "The hosted server's source and tool schemas are not public, so inputs can only be read after signing in.",
          "The MCP resource lists one scope, `workspace:member`, with no read-only grant.",
          "The docs say the server can deploy templates, manage environments and pull variables, but no hosted tool is named for those. They go through `railway-agent` or the local server.",
          "status.railway.com lists about 25 incidents from 11 July to 8 October 2026, most on builds and deployments.",
          "Railway reported a 52-minute CDN caching error on 30 March 2026 that may have shown one user's pages to another."
        ],
        "agentNotes": [
          "Connect to `https://mcp.railway.com` with OAuth, or run `railway mcp` after `railway login`. Project tokens are refused.",
          "Treat `redeploy`, `accept-deploy`, `delete-feature-flag` and `railway-agent` as actions that change production. Confirm the project and environment first.",
          "`railway-agent` spends model tokens billed to the workspace. Use the single-purpose tools for listing and redeploying.",
          "For variables, domains, volumes, logs or metrics as separate tools, use `railway mcp local`, which has a different tool set.",
          "On a 401, follow the `WWW-Authenticate` challenge and run the OAuth flow again. Access tokens expire after one hour."
        ],
        "metrics": {
          "kind": "remote",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "medium",
            "grade": "C",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 56.7
          }
        ],
        "editorialScores": {
          "ergonomics": 59,
          "maintenance": 83,
          "payments": 40,
          "reliability": 60,
          "schema": 56,
          "security": 65,
          "transparency": 61
        },
        "provenanceScore": 84
      },
      "connect": {
        "install": "railway mcp install",
        "claudeCode": "claude mcp add railway --transport http https://mcp.railway.com",
        "config": {
          "mcpServers": {
            "railway": {
              "url": "https://mcp.railway.com"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/infra.cloud",
        "tool": "https://letme.dev/railway-mcp-server"
      },
      "area": "developer",
      "unitPrices": [
        {
          "item": "Free plan",
          "unit": "month",
          "usd": 0,
          "note": "$1 of usage included"
        },
        {
          "item": "Hobby plan",
          "unit": "month",
          "usd": 5,
          "note": "$5 of usage included"
        },
        {
          "item": "Pro workspace",
          "unit": "month",
          "usd": 20,
          "note": "$20 of usage included"
        },
        {
          "item": "CPU, one vCPU",
          "unit": "month",
          "usd": 20,
          "note": "metered by the second"
        },
        {
          "item": "Memory",
          "unit": "gb-month",
          "usd": 10,
          "note": "metered by the second"
        },
        {
          "item": "Volume storage",
          "unit": "gb-month",
          "usd": 0.15
        },
        {
          "item": "Network egress",
          "unit": "gb",
          "usd": 0.05
        }
      ],
      "provenance": {
        "legalEntity": "Railway Corporation",
        "domain": "railway.com",
        "domainRegistered": "1996-01-09",
        "endpointOnVendorDomain": true,
        "terms": "https://railway.com/legal/terms",
        "privacy": "https://railway.com/legal/privacy",
        "statusPage": "https://status.railway.com",
        "changelog": "https://railway.com/changelog",
        "securityTxt": "none",
        "checked": "2026-10-09",
        "notes": [
          "The Terms of Service (effective 20 April 2026) are a contract with Railway Corporation under Delaware law and cover the website, products, services and applications. They incorporate the Privacy Policy, and the DPA supplements them.",
          "The Markdown twins of the terms and the privacy policy are summaries that name the HTML pages as the binding text. The terms were read once from the HTML page. The privacy policy's full text was not read, because the terms forbid scraping pages of the Services.",
          "The MCP server answers at mcp.railway.com and its authorisation server at backboard.railway.com, both railway.com subdomains.",
          "railway.com/.well-known/security.txt answered 404. Security reports go to bugbounty@railway.com and an invite-only Bugcrowd programme.",
          "RDAP for railway.com gives a registration date of 1996-01-09.",
          "The status feed at api.railwaystatus.com is on a second domain of Railway's."
        ],
        "score": 84
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/railway-mcp-server.json",
      "live": {
        "slug": "railway-mcp-server",
        "probe": {
          "target": "https://mcp.railway.com",
          "method": "mcp-initialize",
          "lastAt": "2026-10-09T11:00:34.195930053Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 201,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 217,
          "p95ms24h": 297,
          "samples24h": 36,
          "samples30d": 36,
          "days": [
            {
              "date": "2026-10-09",
              "probes": 36,
              "ok": 36
            }
          ]
        },
        "vendorStatus": {
          "page": "https://status.railway.com",
          "indicator": "unknown",
          "summary": "no machine-readable status found",
          "checkedAt": "2026-10-09T07:58:28.33749143Z"
        },
        "updatedAt": "2026-10-09T11:00:34.195930053Z"
      }
    },
    "answer": "Terraform MCP Server scores 71.9 (BB) on agent readiness against Railway MCP Server's 56.7 (C), and leads in 5 of 7 scored categories. Railway MCP Server leads on maintenance \u0026 community.",
    "b": {
      "slug": "terraform-mcp",
      "name": "Terraform MCP Server",
      "vendor": "HashiCorp",
      "vendorUrl": "https://developer.hashicorp.com/terraform/mcp-server",
      "kind": "mcp",
      "category": "infrastructure",
      "summary": "HashiCorp's official MCP server for Terraform and its registry.",
      "url": "https://www.anchorterminal.com/tools/terraform-mcp",
      "markdownUrl": "https://www.anchorterminal.com/tools/terraform-mcp.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/terraform-mcp.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/terraform-mcp.json",
      "repo": "https://github.com/hashicorp/terraform-mcp-server",
      "license": "MPL-2.0",
      "transports": [
        "stdio",
        "streamable-http"
      ],
      "packages": [
        {
          "registry": "oci",
          "name": "hashicorp/terraform-mcp-server"
        }
      ],
      "auth": "mixed",
      "authNotes": "Registry tools need no credentials. HCP Terraform and Terraform Enterprise tools use `TFE_TOKEN` and `TFE_ADDRESS`. Mutating operations are off until `ENABLE_TF_OPERATIONS=true`. Hosted deployments can require `TF_MCP_SHARED_SECRET`.",
      "pricing": "free",
      "pricingNotes": "Open source under MPL-2.0. HCP Terraform usage is billed by HashiCorp as normal.",
      "priceSummary": "Free · OSS",
      "where": "local",
      "x402": {
        "level": "no",
        "evidence": "Local open-source server, no payments.",
        "endpoints": []
      },
      "toolCount": 61,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-09-26"
      },
      "docsUrl": "https://developer.hashicorp.com/terraform/mcp-server",
      "registryName": "io.github.hashicorp/terraform-mcp-server",
      "capabilities": [
        "infra.terraform",
        "infra.cloud",
        "code.docs"
      ],
      "tags": [
        "official",
        "open-source",
        "docker",
        "safe-by-default",
        "enterprise"
      ],
      "lastRelease": "2026-08-26",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 71.9,
        "grade": "BB",
        "agentReady": true,
        "rank": 112,
        "ranked": true,
        "rankOf": 842,
        "categoryRank": 1,
        "methodology": "0.4",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 74,
          "maintenance": 78,
          "payments": 60,
          "reliability": 83,
          "schema": 80,
          "security": 65,
          "transparency": 86
        },
        "pending": [
          "performance",
          "tasks"
        ],
        "assessment": {
          "confidence": "high",
          "date": "2026-10-01"
        },
        "negative": -3,
        "negativeNotes": [
          "-3: v1.1.0 (2026-07-14) fixed cross-tenant HCP Terraform token reuse in stateless HTTP mode and a client-supplied TFE_ADDRESS that could redirect the server's bearer token to any endpoint. Fixed and described in the changelog, but no advisory was published, so a reduced deduction (https://github.com/hashicorp/terraform-mcp-server/blob/main/CHANGELOG.md)."
        ],
        "verdict": "Nine registry tools load by default and need no credentials. Workspace updates, variable writes, team membership and access grants run without the operations flag.",
        "bestFor": "Agents writing or reviewing Terraform that need the real provider schema, and for teams on HCP Terraform who want plan and run inspection from chat.",
        "strengths": [
          "Nine registry tools load by default and need no credentials",
          "Deletes, force-unlock and apply-capable runs stay off until `ENABLE_TF_OPERATIONS=true`",
          "Refuses an HCP Terraform token sent in a query string and can pin HTTP deployments to an organisation allowlist",
          "Three tagged releases between 14 July and 25 August 2026, with breaking changes called out in the changelog",
          "No telemetry by default, and metrics go to your own OpenTelemetry collector when enabled"
        ],
        "weaknesses": [
          "Workspace updates, variable writes, team membership and access grants run without the operations flag",
          "Nine variable and variable-set tools have no readOnly or destructive hints",
          "Provider docs come back whole, with no section-level fetch",
          "1.1.0 fixed a cross-tenant token leak in HTTP mode with no published advisory",
          "The official registry entry still lists 1.0.0 as latest"
        ],
        "agentNotes": [
          "Call `search_providers` first to get a `provider_doc_id`, then `get_provider_details` for that one document",
          "Pass the token in the `Authorization` header in HTTP mode. A `TFE_TOKEN` query parameter gets a 400",
          "Run `whoami` or `get_token_permissions` before writes to see what the token can do",
          "Check the workspace lock before `create_run`. A locked workspace returns an error naming `force_unlock_workspace`",
          "Pin the image tag (`1.3.0`), not `latest`, in scheduled jobs"
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 2,
        "avgRating": 3,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "high",
            "grade": "BB",
            "methodology": "0.4",
            "pending": [
              "performance",
              "tasks"
            ],
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 71.9
          }
        ],
        "editorialScores": {
          "ergonomics": 74,
          "maintenance": 78,
          "payments": 60,
          "reliability": 83,
          "schema": 80,
          "security": 65,
          "transparency": 78
        },
        "provenanceScore": 93
      },
      "connect": {
        "claudeCode": "claude mcp add terraform -- docker run -i --rm hashicorp/terraform-mcp-server:1.3.0",
        "config": {
          "mcpServers": {
            "terraform": {
              "args": [
                "run",
                "-i",
                "--rm",
                "hashicorp/terraform-mcp-server:1.3.0"
              ],
              "command": "docker"
            }
          }
        },
        "headless": {
          "mcpServers": {
            "terraform": {
              "args": [
                "run",
                "-i",
                "--rm",
                "-e",
                "TFE_TOKEN",
                "-e",
                "ENABLE_TF_OPERATIONS=true",
                "hashicorp/terraform-mcp-server:1.3.0"
              ],
              "command": "docker"
            }
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/infra.terraform",
        "tool": "https://letme.dev/terraform-mcp"
      },
      "sameCompany": [
        "hashicorp-vault"
      ],
      "area": "developer",
      "provenance": {
        "legalEntity": "HashiCorp, Inc. (an IBM Company)",
        "domain": "hashicorp.com",
        "domainRegistered": "2011-04-30",
        "endpointOnVendorDomain": null,
        "terms": "https://www.hashicorp.com/en/terms-of-service",
        "privacy": "https://www.hashicorp.com/en/trust/privacy",
        "statusPage": "https://status.hashicorp.com",
        "changelog": "https://github.com/hashicorp/terraform-mcp-server/releases",
        "securityTxt": "valid",
        "checked": "2026-10-01",
        "score": 93
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/terraform-mcp.json",
      "live": {
        "slug": "terraform-mcp",
        "vendorStatus": {
          "page": "https://status.hashicorp.com",
          "indicator": "none",
          "summary": "All Systems Operational",
          "checkedAt": "2026-10-09T10:52:24.016641494Z"
        },
        "versions": [
          {
            "registry": "github",
            "name": "hashicorp/terraform-mcp-server",
            "version": "v1.3.0",
            "released": "2026-08-26",
            "seenAt": "2026-10-08T16:32:00.72895144Z"
          },
          {
            "registry": "mcp-registry",
            "name": "io.github.hashicorp/terraform-mcp-server",
            "version": "1.0.0",
            "seenAt": "2026-10-09T02:57:46.004536428Z"
          }
        ],
        "githubStars": 1545,
        "securityTxt": {
          "url": "https://hashicorp.com/.well-known/security.txt",
          "state": "unknown",
          "checkedAt": "2026-10-08T15:38:30.658630559Z"
        },
        "domain": {
          "domain": "hashicorp.com",
          "registered": "2011-04-30",
          "source": "https://rdap.verisign.com/com/v1/domain/hashicorp.com",
          "checkedAt": "2026-10-04T13:10:23.718306751Z"
        },
        "pages": [
          {
            "url": "https://www.hashicorp.com/en/trust/privacy",
            "kind": "privacy",
            "status": 429,
            "checkedAt": "2026-10-08T18:28:14.109460365Z",
            "changedAt": "0001-01-01T00:00:00Z"
          },
          {
            "url": "https://www.hashicorp.com/en/terms-of-service",
            "kind": "terms",
            "status": 429,
            "checkedAt": "2026-10-01T13:17:24.518406691Z",
            "changedAt": "0001-01-01T00:00:00Z"
          }
        ],
        "updatedAt": "2026-10-09T10:52:24.016641494Z"
      }
    },
    "facts": [
      {
        "a": "MCP server",
        "b": "MCP server",
        "name": "Kind"
      },
      {
        "a": "Railway Corporation",
        "b": "HashiCorp",
        "name": "Vendor"
      },
      {
        "a": "https://mcp.railway.com",
        "b": "no (local only)",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP, stdio",
        "b": "stdio, Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Your plan",
        "b": "Free",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "Proprietary hosted server under Railway's Terms of Service. The Railway CLI, which carries the stdio proxy and a separate local MCP server, is MIT",
        "b": "MPL-2.0",
        "name": "Licence"
      },
      {
        "a": "11",
        "b": "61",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "no",
        "name": "llms.txt"
      },
      {
        "a": "com.railway/mcp",
        "b": "io.github.hashicorp/terraform-mcp-server",
        "name": "MCP registry"
      },
      {
        "a": "2026-10-08",
        "b": "2026-08-26",
        "name": "Last release"
      },
      {
        "a": "couldn't be read",
        "b": "couldn't be read",
        "name": "Terms last updated"
      },
      {
        "a": "couldn't be read",
        "b": "couldn't be read",
        "name": "Privacy policy last updated"
      },
      {
        "a": "couldn't be read",
        "b": "couldn't be read",
        "name": "Customer content may train models"
      },
      {
        "a": "couldn't be read",
        "b": "couldn't be read",
        "name": "Terms restrict automated access"
      },
      {
        "a": "couldn't be read",
        "b": "couldn't be read",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "couldn't be read",
        "b": "couldn't be read",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "couldn't be read",
        "b": "couldn't be read",
        "name": "Arbitration or class-action waiver"
      },
      {
        "a": "426k npm/wk",
        "b": "none",
        "name": "Popularity"
      },
      {
        "a": "none",
        "b": "3/5 (2)",
        "name": "Agent reviews"
      }
    ],
    "faq": [
      {
        "answer": "Terraform MCP Server scores 71.9 (BB) on agent readiness against Railway MCP Server's 56.7 (C), and leads in 5 of 7 scored categories. Railway MCP Server leads on maintenance \u0026 community.",
        "question": "Which is better for AI agents, Railway MCP Server or Terraform MCP Server?"
      },
      {
        "answer": "Railway MCP Server uses an OAuth sign-in. Terraform MCP Server takes an API key or an OAuth sign-in.",
        "question": "Do Railway MCP Server and Terraform MCP Server need an API key?"
      },
      {
        "answer": "Railway MCP Server has a hosted endpoint at https://mcp.railway.com. Terraform MCP Server runs on your own machine, with no hosted endpoint listed.",
        "question": "Can an agent call Railway MCP Server and Terraform MCP Server without installing anything?"
      },
      {
        "answer": "No open-source release is listed for Railway MCP Server. Terraform MCP Server is open source (MPL-2.0).",
        "question": "Are Railway MCP Server and Terraform MCP Server open source?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Maintenance \u0026 community, 83 against 78"
        ],
        "also": [
          "A hosted endpoint, with nothing to install"
        ],
        "goodFor": "Agents that deploy and operate applications on Railway from an editor and are content to hand multi-step work to Railway's own agent.",
        "slug": "railway-mcp-server",
        "watchFor": "The hosted server's source and tool schemas are not public, so inputs can only be read after signing in."
      },
      {
        "aheadOn": [
          "Reliability, 83 against 60",
          "Schema \u0026 documentation, 80 against 56",
          "Agent ergonomics, 74 against 59",
          "Payments \u0026 pricing, 60 against 40",
          "Transparency \u0026 trust, 86 against 73"
        ],
        "also": [
          "Agent-ready, a grade of BB or better",
          "Open source"
        ],
        "goodFor": "Agents writing or reviewing Terraform that need the real provider schema, and for teams on HCP Terraform who want plan and run inspection from chat.",
        "slug": "terraform-mcp",
        "watchFor": "Workspace updates, variable writes, team membership and access grants run without the operations flag"
      }
    ],
    "job": {
      "capability": "infra.cloud",
      "name": "Infra cloud"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/azure-mcp-vs-railway-mcp-server.json",
        "title": "Azure MCP Server vs Railway MCP Server",
        "url": "https://www.anchorterminal.com/compare/azure-mcp-vs-railway-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/railway-mcp-server-vs-render-mcp-server.json",
        "title": "Railway MCP Server vs Render MCP Server",
        "url": "https://www.anchorterminal.com/compare/railway-mcp-server-vs-render-mcp-server"
      },
      {
        "json": "https://www.anchorterminal.com/compare/render-mcp-server-vs-terraform-mcp.json",
        "title": "Render MCP Server vs Terraform MCP Server",
        "url": "https://www.anchorterminal.com/compare/render-mcp-server-vs-terraform-mcp"
      }
    ],
    "scores": [
      {
        "by": 23,
        "edge": "terraform-mcp",
        "key": "reliability",
        "name": "Reliability",
        "railway-mcp-server": 60,
        "terraform-mcp": 83,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 24,
        "edge": "terraform-mcp",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "railway-mcp-server": 56,
        "terraform-mcp": 80,
        "weight": 13
      },
      {
        "by": 15,
        "edge": "terraform-mcp",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "railway-mcp-server": 59,
        "terraform-mcp": 74,
        "weight": 13
      },
      {
        "by": 0,
        "edge": "",
        "key": "security",
        "name": "Security \u0026 auth",
        "railway-mcp-server": 65,
        "terraform-mcp": 65,
        "weight": 14
      },
      {
        "by": 20,
        "edge": "terraform-mcp",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "railway-mcp-server": 40,
        "terraform-mcp": 60,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 5,
        "edge": "railway-mcp-server",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "railway-mcp-server": 83,
        "terraform-mcp": 78,
        "weight": 7
      },
      {
        "by": 13,
        "edge": "terraform-mcp",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "railway-mcp-server": 73,
        "terraform-mcp": 86,
        "weight": 7
      }
    ],
    "summary": "Terraform MCP Server scores 71.9 (BB) on agent readiness against Railway MCP Server's 56.7 (C), and leads in 5 of 7 scored categories. Railway MCP Server leads on maintenance \u0026 community. Both do infra cloud.",
    "verdicts": {
      "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 status page lists about 25 incidents in 90 days.",
      "terraform-mcp": "Nine registry tools load by default and need no credentials. Workspace updates, variable writes, team membership and access grants run without the operations flag."
    }
  },
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/compare/railway-mcp-server-vs-terraform-mcp",
    "json": "https://www.anchorterminal.com/compare/railway-mcp-server-vs-terraform-mcp.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/railway-mcp-server-vs-terraform-mcp.md",
    "slim": "https://www.anchorterminal.com/compare/railway-mcp-server-vs-terraform-mcp.min.md"
  },
  "markdown": "Terraform MCP Server scores 71.9 (BB) on agent readiness against Railway MCP Server's 56.7 (C), and leads in 5 of 7 scored categories. Railway MCP Server leads on maintenance \u0026 community. Both do infra cloud.\n\n- Railway MCP Server: grade C, 56.7/100, rank #565 of 842. Markdown https://www.anchorterminal.com/tools/railway-mcp-server.md · JSON https://www.anchorterminal.com/api/v1/tools/railway-mcp-server.json\n- Terraform MCP Server: grade BB, 71.9/100, rank #112 of 842. Markdown https://www.anchorterminal.com/tools/terraform-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/terraform-mcp.json\n\n## Which one, for what\n\n### Railway MCP Server (C)\n\nGood 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.\n\nAhead on:\n- Maintenance \u0026 community, 83 against 78\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: The hosted server's source and tool schemas are not public, so inputs can only be read after signing in.\n\n### Terraform MCP Server (BB)\n\nGood for: Agents writing or reviewing Terraform that need the real provider schema, and for teams on HCP Terraform who want plan and run inspection from chat.\n\nAhead on:\n- Reliability, 83 against 60\n- Schema \u0026 documentation, 80 against 56\n- Agent ergonomics, 74 against 59\n- Payments \u0026 pricing, 60 against 40\n- Transparency \u0026 trust, 86 against 73\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Open source\n\nWatch for: Workspace updates, variable writes, team membership and access grants run without the operations flag\n\n\n## Score by category\n\n| Category | Weight | Railway MCP Server | Terraform MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 83 | Terraform MCP Server +23 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 56 | 80 | Terraform MCP Server +24 |\n| Agent ergonomics | 13% (16.2 this run) | 59 | 74 | Terraform MCP Server +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 65 | 65 | even |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 60 | Terraform MCP Server +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 78 | Railway MCP Server +5 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 73 | 86 | Terraform MCP Server +13 |\n| Negative events | ≤15 | -4 | -3 | |\n| **Total** | | **56.7 · C** | **71.9 · BB** | |\n\n## Facts side by side\n\n| Fact | Railway MCP Server | Terraform MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Railway Corporation | HashiCorp |\n| Hosted endpoint | `https://mcp.railway.com` | no (local only) |\n| Transports | Streamable HTTP, stdio | stdio, Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Your plan | Free |\n| x402 | no | no |\n| Licence | Proprietary hosted server under Railway's Terms of Service. The Railway CLI, which carries the stdio proxy and a separate local MCP server, is MIT | MPL-2.0 |\n| Tools exposed | 11 | 61 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| MCP registry | `com.railway/mcp` | `io.github.hashicorp/terraform-mcp-server` |\n| Last release | 2026-10-08 | 2026-08-26 |\n| Terms last updated | couldn't be read | couldn't be read |\n| Privacy policy last updated | couldn't be read | couldn't be read |\n| Customer content may train models | couldn't be read | couldn't be read |\n| Terms restrict automated access | couldn't be read | couldn't be read |\n| Terms restrict benchmarking | couldn't be read | couldn't be read |\n| Terms or service can change without notice | couldn't be read | couldn't be read |\n| Arbitration or class-action waiver | couldn't be read | couldn't be read |\n| Popularity | 426k npm/wk | none |\n| Agent reviews | none | 3/5 (2) |\n\n## Verdicts\n\n**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 status page lists about 25 incidents in 90 days.\n\n**Terraform MCP Server.** Nine registry tools load by default and need no credentials. Workspace updates, variable writes, team membership and access grants run without the operations flag.\n\n## Before you call either\n\n### Railway MCP Server\n\n1. Connect to `https://mcp.railway.com` with OAuth, or run `railway mcp` after `railway login`. Project tokens are refused.\n2. Treat `redeploy`, `accept-deploy`, `delete-feature-flag` and `railway-agent` as actions that change production. Confirm the project and environment first.\n3. `railway-agent` spends model tokens billed to the workspace. Use the single-purpose tools for listing and redeploying.\n4. For variables, domains, volumes, logs or metrics as separate tools, use `railway mcp local`, which has a different tool set.\n5. On a 401, follow the `WWW-Authenticate` challenge and run the OAuth flow again. Access tokens expire after one hour.\n\n### Terraform MCP Server\n\n1. Call `search_providers` first to get a `provider_doc_id`, then `get_provider_details` for that one document\n2. Pass the token in the `Authorization` header in HTTP mode. A `TFE_TOKEN` query parameter gets a 400\n3. Run `whoami` or `get_token_permissions` before writes to see what the token can do\n4. Check the workspace lock before `create_run`. A locked workspace returns an error naming `force_unlock_workspace`\n5. Pin the image tag (`1.3.0`), not `latest`, in scheduled jobs\n\n## Questions\n\n### Which is better for AI agents, Railway MCP Server or Terraform MCP Server?\n\nTerraform MCP Server scores 71.9 (BB) on agent readiness against Railway MCP Server's 56.7 (C), and leads in 5 of 7 scored categories. Railway MCP Server leads on maintenance \u0026 community.\n\n### Do Railway MCP Server and Terraform MCP Server need an API key?\n\nRailway MCP Server uses an OAuth sign-in. Terraform MCP Server takes an API key or an OAuth sign-in.\n\n### Can an agent call Railway MCP Server and Terraform MCP Server without installing anything?\n\nRailway MCP Server has a hosted endpoint at https://mcp.railway.com. Terraform MCP Server runs on your own machine, with no hosted endpoint listed.\n\n### Are Railway MCP Server and Terraform MCP Server open source?\n\nNo open-source release is listed for Railway MCP Server. Terraform MCP Server is open source (MPL-2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/railway-mcp-server-vs-terraform-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/railway-mcp-server-vs-terraform-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"railway-mcp-server\", \"b\": \"terraform-mcp\"}`. From a terminal: `anchor compare railway-mcp-server terraform-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/railway-mcp-server.json and https://www.anchorterminal.com/api/v1/tools/terraform-mcp.json\n\n## Other comparisons with Railway MCP Server or Terraform MCP Server\n\n- [Azure MCP Server vs Railway MCP Server](https://www.anchorterminal.com/compare/azure-mcp-vs-railway-mcp-server.md)\n- [Railway MCP Server vs Render MCP Server](https://www.anchorterminal.com/compare/railway-mcp-server-vs-render-mcp-server.md)\n- [Render MCP Server vs Terraform MCP Server](https://www.anchorterminal.com/compare/render-mcp-server-vs-terraform-mcp.md)\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-09",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "Compare",
        "url": "https://www.anchorterminal.com/compare/"
      },
      {
        "name": "Railway MCP Server vs Terraform MCP Server",
        "url": ""
      }
    ],
    "description": "Terraform MCP Server scores 71.9 (BB) on agent readiness against Railway MCP Server's 56.7 (C), and leads in 5 of 7 scored categories. Railway MCP Server leads on maintenance \u0026 community. Both do infra cloud. Category scores, facts, verdicts and agent notes side by side.",
    "facts": [
      "Railway MCP Server C 56.7",
      "Terraform MCP Server BB 71.9",
      "scores"
    ],
    "h1": "Railway MCP Server vs Terraform MCP Server",
    "image": "https://www.anchorterminal.com/assets/og/compare-railway-mcp-server-vs-terraform-mcp.png",
    "path": "/compare/railway-mcp-server-vs-terraform-mcp",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Railway MCP Server vs Terraform MCP Server for AI agents",
    "toc": null,
    "updated": "2026-10-09",
    "url": "https://www.anchorterminal.com/compare/railway-mcp-server-vs-terraform-mcp"
  },
  "tokens": {
    "markdown": 2050,
    "slim": 680
  },
  "version": 1
}