Self-hosted Cloudflare MCP alternatives
Cloudflare's MCP servers are hosted-only. You reach them over OAuth at Cloudflare's endpoints, and there is no build you install and run yourself. If you need the server process and its credentials on your own machine, you need a different one.
Every server below installs locally over stdio. The caveat is the same as always: keeping the process local controls where the tokens live, but each cloud's API still receives the calls that provision and read your infrastructure. Each pick names the platform it manages.
The 8 best self-hosted alternatives
AWS Labs' server installs locally and runs any AWS CLI command from an agent, with validation, read-only mode, and command suggestions. The broadest self-hosted cloud surface here, all driven from a process you control.
Set up AWS (AWS Labs) →- AzureOfficial
Running on your own machine, Microsoft's official Azure server manages 40+ Azure services: storage, Key Vault, Cosmos DB, SQL, Monitor, AKS, App Service, and more. A full cloud, locally hosted.
Set up Azure → - DigitalOceanOfficial
DigitalOcean's official server self-hosts and manages App Platform, Droplets, managed databases, Kubernetes, networking, storage, and GenAI. VMs and managed services from a local install.
Set up DigitalOcean → - Google Cloud RunOfficial
Google Cloud's official Cloud Run server runs locally, deploying local code to Cloud Run, listing and inspecting services, and reading logs. Deploy-focused, on a process you host.
Set up Google Cloud Run → - HerokuOfficial
Heroku's official Platform server installs locally and deploys apps, scales dynos, manages add-ons and pipelines, runs one-off commands, and operates Postgres. The classic app-platform workflow, self-hosted.
Set up Heroku → - NetlifyOfficial
Closest on frontend hosting: Netlify's official server runs locally and creates, deploys, and manages projects, env vars, forms, access controls, and extensions. The self-hosted equivalent of Cloudflare's developer focus.
Set up Netlify → Adjacent rather than a deploy target: Grafana Labs' official server self-hosts and queries dashboards, Prometheus, Loki, incidents, alerts, and OnCall. It watches the infrastructure you run rather than provisioning it.
Set up Grafana →A local data store, not a cloud: Bytebase DBHub runs an agent against a SQLite database file over stdio with execute_sql and search_objects. Of everything here it keeps the most on disk, with no remote API at all.
Set up SQLite (DBHub) →
How to choose
Since Cloudflare cannot be self-hosted, the closest local clouds are AWS and Azure for breadth, DigitalOcean for VMs and managed services, and Netlify for frontend hosting like Cloudflare's developer angle. GCP and Heroku center on deploys. Grafana is monitoring rather than provisioning, and SQLite through DBHub is a plain local data file. Running any of them keeps the process and tokens yours, though each cloud's API still receives the provisioning calls. SQLite is the exception, staying fully on disk.
FAQ
- Can the Cloudflare MCP server be self-hosted?
- No. Cloudflare offers only hosted remote servers reached over OAuth, with no self-installable build. If running the server yourself is a hard requirement, pick one of the alternatives that ships a local stdio command, such as AWS, Azure, DigitalOcean, or Netlify.
- Does running these locally keep my cloud data on my own infrastructure?
- It keeps the server process and its credentials local, which is usually the point. AWS, Azure, DigitalOcean, GCP, Heroku, and Netlify still call their respective cloud APIs to provision and read resources. SQLite through DBHub is the exception, since it reads a local database file and never leaves your machine.