Cloudflare vs Self-Hosted vs Managed MCP: A Real Comparison
Three genuinely different ways to run an MCP server: Cloudflare's DIY edge framework, fully self-hosted infrastructure, and a managed platform. Here is what each one actually asks of you.
These three options get compared often, but they're not three versions of the same thing. Cloudflare gives you a framework and edge compute. Self-hosting gives you full control and full responsibility. A managed platform gives you a working server without touching infrastructure. Here's what each actually requires.
Cloudflare Workers + Agents SDK
Cloudflare's offering here is a DIY framework, not managed MCP hosting. You build your MCP server using the McpAgent class and Cloudflare's workers-oauth-provider library, then deploy it to Workers. Cloudflare provides the edge compute, an AI Playground for testing, and OAuth 2.1 tooling, but you are the one assembling the server, wiring up authentication, and deciding how tools are structured.
What you get: Cloudflare's global edge network, a purpose-built SDK for MCP specifically, and billing through standard Workers/Durable Objects pricing rather than a separate MCP fee.
What you build yourself: the actual tool logic, your authentication configuration using their OAuth library, rate limiting beyond whatever Workers provides by default, and monitoring beyond generic Workers metrics.
Best fit: teams that want to build on Cloudflare's infrastructure specifically, are comfortable working directly with a Workers-based SDK, and don't need MCP-specific analytics or a browser-based tool builder.
Fully Self-Hosted
Rent a VPS, run your own Node.js or Python process, put Nginx in front of it for TLS, and manage the whole stack yourself.
What you get: complete control over the network path, the runtime, and where the process physically runs, which matters for specific compliance requirements.
What you build yourself: everything. HTTPS certificate provisioning and renewal, process management and restart-on-crash behavior, authentication, secrets storage, rate limiting, and a logging or observability stack. None of this is unique to MCP, but all of it has to exist before a self-hosted server is genuinely production-ready.
Best fit: teams that already run infrastructure they trust, have staff who maintain it, or have a compliance requirement that specifically mandates running on their own infrastructure.
Managed MCP Hosting
A platform built specifically for MCP servers, like MCPCore, provisions the HTTPS endpoint, subdomain, authentication, encrypted secrets, rate limiting, and analytics automatically. You write tool code and it's live immediately.
What you get: a production-ready endpoint without provisioning anything, four authentication modes you can switch per server without touching tool code, and analytics built in from the start.
What you give up: direct control over the underlying compute and network. For most teams this doesn't matter. For a small number with specific data-residency or on-premises requirements, it can, which is why MCPCore's Enterprise plan includes a self-hosted Docker option that keeps the platform's built-in tooling while running inside your own environment.
Best fit: teams that want to ship tools quickly and would rather spend engineering time on the tools themselves than on the infrastructure underneath them.
Side-by-Side
| Cloudflare Workers | Self-Hosted | MCPCore | |
|---|---|---|---|
| Setup time | Hours (framework, still your code) | Hours to days | Minutes |
| Infrastructure you manage | Workers config, OAuth wiring | Everything | None |
| Built-in analytics | No, generic Workers metrics only | No, build it yourself | Yes, per-tool |
| Auth options | OAuth via their library, build it yourself otherwise | Build it yourself | 4 built-in modes |
| Compliance-friendly self-hosting | N/A, it's already Cloudflare's infra | Yes, by definition | Yes, via Enterprise Docker option |
| Cost model | Workers/Durable Objects pricing | VPS cost + your time | Free tier, then per-plan pricing |
Which One Actually Fits
If you want Cloudflare's edge network specifically and don't mind assembling the pieces yourself, their SDK is a legitimate, actively maintained option. If you have a hard requirement to run on infrastructure you fully control, self-hosting is the only option that satisfies that, and it's worth budgeting real time for the parts beyond just running the process. If your priority is shipping working tools without becoming the person who maintains a reverse proxy, a managed platform removes that entire layer, and MCPCore's Enterprise self-hosted option exists specifically for teams that want the managed experience without giving up control of where it physically runs.
Third-party product details reflect information available as of mid-2026 and may change. Verify current specifics directly with Cloudflare before building on their SDK for a production workload.