Cloudflare MCP vs Netlify MCP vs Railway Skills (2026)
A. Frans
Published August 31, 2026
Table of Contents
Three hosting companies now ship a first-party way for a coding agent to touch your account, and they picked three different architectures to do it. Cloudflare runs a fleet of remote servers you connect to by URL. Netlify publishes an npm package that wraps its API and CLI. Railway ships a shell installer that sets up the CLI, the skill, and the MCP config in one pass.
Those choices aren't cosmetic. They determine where your credentials live, what happens when the vendor ships a breaking change, and how much of your production surface the agent can reach on a bad day.
I checked all three against their repositories on 2026-08-31. One of them has an archived component still being recommended around the web, which is the kind of thing worth knowing before you paste a command.
Side by side
| Cloudflare | Netlify | Railway | |
|---|---|---|---|
| Repo | cloudflare/mcp-server-cloudflare | netlify/netlify-mcp | railwayapp/railway-skills |
| Architecture | Remote servers over Streamable HTTP | Local npm package (@netlify/mcp) | CLI + skill + hosted MCP |
| Servers | 16 domain-specific, plus a separate Code Mode server | One | One hosted |
| License | Apache-2.0 | Not declared in repo metadata | MIT |
| Auth | OAuth against your Cloudflare account | Netlify account via CLI | railway login, or OAuth via the Claude connector |
| Runs code locally | No | Yes (Node 22+) | Yes |
| Last push checked | 2026-08-24 | 2026-08-13 | 2026-08-12 |
| Best for | Reading production state safely | Full project lifecycle on Netlify | Terminal-first Railway workflows |
Cloudflare: sixteen small servers instead of one big one
Cloudflare's repo doesn't ship a single MCP server. It ships sixteen, each scoped to a product area, and each reachable at its own URL:
https://docs.mcp.cloudflare.com/mcp documentation
https://bindings.mcp.cloudflare.com/mcp Workers storage, AI, compute
https://builds.mcp.cloudflare.com/mcp Workers Builds
https://observability.mcp.cloudflare.com/mcp logs and analytics
https://browser.mcp.cloudflare.com/mcp page fetch, markdown, screenshots
https://radar.mcp.cloudflare.com/mcp internet insights
https://auditlogs.mcp.cloudflare.com/mcp audit log queries
There are nine more, covering containers, Logpush, AI Gateway, AutoRAG, DNS analytics, digital experience monitoring, CASB, the Cloudflare blog, and a demo server.
You connect any MCP client that supports remote servers straight to a URL. In Claude Code:
claude mcp add --transport http cloudflare-observability https://observability.mcp.cloudflare.com/mcp
Nothing runs on your machine. Authentication is OAuth against your Cloudflare account, so there's no API token sitting in a config file waiting to be committed by accident.
The split design is the interesting part, and it's a security decision dressed up as an organizational one. Adding the observability server gives an agent read access to your logs and analytics and nothing else. Adding the bindings server lets it touch Workers storage. You choose your blast radius per server rather than accepting one token that can do everything.
Cloudflare also maintains a separate Code Mode server at mcp.cloudflare.com, in the cloudflare/mcp repo, which trades curated typed tools for broad API coverage through code execution. Their own guidance is to use the domain-specific servers when you're working inside one product area and Code Mode when you need reach across many. That's the right way around, and I'd add: start with the narrow ones. Broad API coverage through code execution is a lot of rope.
One legacy note from the repo. Every server exposes the same handler at /mcp and /sse, but a legacy SSE GET /sse request now returns 410 Gone with migration instructions. If you set this up months ago and it stopped working, that's why. Point your config at /mcp.
Netlify: one package, the whole lifecycle
Netlify's server is netlify/netlify-mcp, published on npm as @netlify/mcp, version 1.15.1 at the time of writing. It runs locally and wraps both the Netlify API and the Netlify CLI.
claude mcp add netlify -- npx -y @netlify/mcp
Requirements are Node.js 22 or higher and a Netlify account. The repo recommends installing netlify-cli globally for the best experience, and given the server wraps the CLI, that's less a suggestion than a dependency you should plan for.
Scope is the widest of the three. From the README: create, manage, and deploy projects; modify access controls; install and uninstall extensions; fetch user and team information; enable and manage form submissions; and create and manage environment variables and secrets.
Read that list again with an adversarial eye. An agent with this server connected can change access controls and read your environment secrets. That is a coherent design for a tool meant to do real work, and it is also the widest permission grant of the three by a distance. If you connect it, connect it to a personal or staging Netlify account first and watch what it does before you point it at anything with customers on it.
The repo carries no declared license in its metadata, which is worth noting if you're at a company where legal reviews dependencies. It's a small thing and probably an oversight, but "probably an oversight" isn't what a license review accepts.
Railway: the installer that does everything, and one archived trap
Railway took the most opinionated path. One command:
curl -fsSL agents.railway.com | sh
That installs the Railway CLI, installs the skills, configures the Railway MCP server for whatever tools it detects on your machine, and checks your authentication. If you're not logged in, railway login. If the CLI is already there, railway setup agent does the configuration half on its own.
You should read a shell script before piping it to sh. That's true here and it's true everywhere, and the fact that it's a first-party Railway domain doesn't change the rule.
Railway also publishes a hosted connector in Claude's connector directory, which uses OAuth and their hosted MCP server and skips the CLI entirely. For most people that's the better door. Use the installer when you want the terminal workflow with the use-railway skill and hooks; use the connector when you just want the agent to reach your Railway account.
Now the trap. railwayapp/railway-mcp-server is archived — last push 2026-05-23, still sitting there with 192 stars and a description that reads "Official Railway MCP Server." It's been superseded by the hosted server that the installer configures. Plenty of blog posts and directory listings still point at it. If you install from that repo you'll get something that hasn't been touched in three months.
This is the general case, not a Railway-specific complaint. Directory entries go stale faster than repos do. Check the archived flag on GitHub before you install anything, including entries you find on this site.
Which one to pick
If you're already on the platform, use that platform's integration. There's no cross-platform winner here and picking by feature list would be silly.
If you're choosing where to start, start with Cloudflare's observability or docs server. Not because Cloudflare is better, but because those two servers are read-only against a bounded product area, and the first MCP server you connect to a production account should be one that can't change anything. Get a feel for how the agent uses it. Then widen.
If you want the most capability per install, it's Netlify, and the price is that you've granted secret access and access-control changes to a local process. Make that trade knowingly.
If you're on Railway, take the connector over the installer unless you specifically want the terminal skill, and do not install from the archived MCP server repo.
Three things to check before any of them
Where does the credential live? Cloudflare's remote servers use OAuth and hold nothing locally. Netlify and Railway authenticate through a local CLI. Neither is wrong. Only one of them leaves something on your laptop.
What's the narrowest server that does the job? Cloudflare makes this easy by shipping sixteen. With Netlify and Railway you get one server and the full permission set, so the scoping has to happen at the account level — separate account, separate project, staging first.
Is the repo still alive? Last push date and the archive flag, every time. It takes ten seconds and it's the check that would have saved anyone still installing Railway's old server. Our guide on verifying a Claude Code install command covers the rest of that process, and if you're still deciding between these and a locally-defined skill, MCP servers vs agent skills draws the line.
FAQ
Can I connect all three at once? Yes, and there's no technical conflict. But every connected server adds tool definitions to the agent's context, and a crowded tool list makes tool selection worse, not better. Connect the platform you deploy to and leave the others out until you need them.
Do I need the Railway CLI if I use the Claude connector? No. The connector uses Railway's hosted MCP server with OAuth. The CLI path exists for people who want the use-railway skill and hooks in a terminal workflow.
Why does Cloudflare ship sixteen servers instead of one? Curated, typed tools for a specific product area versus broad coverage through code execution. That's their stated split, with the Code Mode server covering the broad case. The practical effect is per-server permission scoping, which is the strongest security story of the three.
Is @netlify/mcp safe to run with npx -y? The -y flag skips the install prompt, which means you get whatever @netlify/mcp resolves to at that moment. It's a first-party package under Netlify's npm scope, so the supply-chain risk is Netlify's account security rather than a typosquat. Pin a version if that distinction matters at your company.
What happened to the old Railway MCP server? Archived on GitHub, superseded by Railway's hosted MCP server. The repo is still public and still turns up in search results, which is exactly why it's worth naming.
Share this article
⚙Related Tools
📄Related Articles
Get More AI Tool Guides
New comparisons and guides every week. Join thousands of professionals staying ahead of the AI curve.