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.
| Evidence field | RailwayWatchlist candidate | buildkiteMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP com.railway · Publisher source ↗ | First-party MCP ecosystem:buildkite · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Stale Repo: Not documented Package: Not documented | Repo: Aug 13, 2026 Package: Not documented |
| Popularity evidence | ||
| GitHub stars | Not documented | 52 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| Client coverage | ||
| Client coverage details | Not documented | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP |
| 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. | Hosted access uses short-lived OAuth, while headless and local deployments use scoped Buildkite API tokens. |
| Cost | Railway resource/deployment usage and account-plan charges apply. | The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply. |
| Permissions | Can mutate projects/deployments/services according to the authorized Railway user/scope. Hosted and local modes expose different tool surfaces. | OAuth and API-token scopes govern organization, pipeline, build, job, artifact, and Test Engine access; a read-only hosted endpoint is available. |
| Data handling | Project metadata, variables requested by tools and deployment context can be shared with the AI client/provider. | Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive cloud & devops information. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Deployment mutation and potentially sensitive environment/project information require scope control and confirmation. | Write-capable endpoints can rerun, cancel, or otherwise change CI state; use the read-only endpoint for investigation. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review. |
| Evidence date | ||
| Editorial review | 2026-09-13T00:00:00Z | 2026-07-30 |
| Candidate evidence | 2026-09-13T00:00:00Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →