Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

RailwayTerraform MCP

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedPlaywright MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	RailwayShortlist candidate	Terraform MCPMCP100 Recommended
Task fit
Best for	Railway users who want project, environment and deployment workflows through an OAuth-scoped hosted MCP service.	Connect compatible AI clients to HashiCorp's documented MCP capabilities.
Not ideal for	Users who need a read-only server or who expect hosted and local Railway MCP modes to have identical tools.	Users who need a fully reviewed MCP100 recommendation today
Avoid when	Avoid broad workspace/project authorization or destructive deployment operations when a narrower OAuth scope is sufficient.	Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details	First-party MCP com.railway · Publisher source ↗	First-party MCP HashiCorp · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Aug 14, 2026 Package: Not documented
Popularity evidence
GitHub stars	Not documented	1,534 GitHub stars · checked 2026-09-25T18:35:00Z
Shared repository stars	625 Shared repository stars (not MCP-specific) · checked 2026-10-21	Not documented
Client coverage
Client coverage details	Not documented	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	Hosted server uses Railway OAuth and can scope authorized workspaces/projects; local mode reuses Railway CLI login.	HCP Terraform/TFE API tokens; remote client may pass per-user TFE_TOKEN
Cost	Railway resource/deployment usage and account-plan charges apply.	HCP/TFE/run costs may apply
Permissions	Can mutate projects/deployments/services according to the authorized Railway user/scope. Hosted and local modes expose different tool surfaces.	HCP Terraform/TFE RBAC
Data handling	Project metadata, variables requested by tools and deployment context can be shared with the AI client/provider.	registry/HCP/TFE data may reach connected MCP client/LLM
Limitations
Tradeoffs	Promoted after strict re-audit: canonical identity and MCP-native/publisher-backed implementation are sufficiently evidenced, with real workflow value, usable documentation, understandable permissions, plausible maintenance, and no unresolved security veto. Still not strong enough for Recommended.	Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk context	Deployment mutation and potentially sensitive environment/project information require scope control and confirmation.	stdio/localhost defaults; strict CORS; TLS verify on; rate limits; ENABLE_TF_OPERATIONS=false by default
Evidence date
Editorial review	2026-10-21	2026-07-24
Candidate evidence	2026-10-21T00:00:00Z	2026-09-25T18:35:00Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →