Allows read-only inspection of Cloudflare DNS records, rule sets, tunnels and routes, Zero Trust apps, and other read-only paths. It also enables requesting changes such as creating, updating, or deleting a single DNS record or adding, changing, or removing a tunnel route, with each change requiring confirmation through a ticket.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Coolify-Cloudflare-MCP why is my blog app unhealthy? check its latest deployment logs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Works withCoolify and Cloudflare. Not made by or affiliated with Coolify or Cloudflare.
Coolify-Cloudflare-MCP is a small server you run yourself. It gives your AI app two things. First, a free look at everything: your apps, deployments, logs, DNS records, tunnels and rule sets. Second, a way to ask for changes, like a deploy, a restart or a new DNS record. Each change becomes a ticket, and nothing runs until you open your own Confirm page and tap Confirm.
This is for people who run apps on their own server with Coolify and keep their domains on Cloudflare, and who want an AI to help check on things from a laptop or a phone without handing it the keys.
You: Why is my "blog" app showing as unhealthy?
AI: It crashed 4 minutes ago. The last deployment log ends with "Error: port 3000 already in use".
I can restart it. That needs your tap on the Confirm page.
You: Yes, restart it.
AI: I made ticket T-4821: "Restart app blog". Open your Confirm page and tap Confirm.
(you tap Confirm)
AI: Done. The blog is running again and the health check is green.This server can change a real server and a real Cloudflare account. The safety comes from the Confirm page, soread every ticket before you tap, and start with the read-only tokens. Read docs/safety.md first.
Looking is free, changing is a ticket. Every change waits for your tap on a separate page. One tap, one action, never a batch.
The AI never writes the ticket. The server builds the text from checked arguments, so the AI cannot hide what a change really does.
Frozen on request. One button on the Confirm page freezes every change, and READ_ONLY=1 removes the ability to even ask.
Secrets stay hidden. Passwords, tokens and keys show as *** in answers and logs. No tool takes a password.
Two locks on the Confirm page. It sits behind Cloudflare Zero Trust, and the server checks the signed token and your email itself.
Small, fenced reach. Cloudflare changes cover only DNS records and one tunnel's routes, only inside one zone, and always with a separate edit token. Coolify cannot delete apps through this tool.
Nothing collected. No account, no cloud service of ours, no tracking. The only outside calls go to your own Coolify and to Cloudflare's API.
You see everything. One action log records what was asked, tapped, run or refused, without secret values.
The terminal is a real shell. If you switch on the optional terminal, it can do whatever its SSH user can do. Read the terminal section first.
More in docs/safety.md, docs/privacy.md and docs/threat-model.md.
Related MCP server: Coolify MCP Server
More in docs/how-it-works.md.
Word | What it means here |
Ticket | A change waiting for your tap. It says exactly what will happen. |
Confirm page | Your own web page where you tap Confirm or Deny on a ticket. |
Frozen | No change can run. The server starts frozen, and you unfreeze it on the Confirm page. |
Typed word | For risky tickets (deletes, tunnel routes) you must also type a word, like the host name. |
Coolify | A self-hosted platform for running apps on your own server. |
Zero Trust | Cloudflare's login gate. It keeps strangers away from the Confirm page. |
AI app | Claude or any app that can use tools through MCP. |
MCP | Model Context Protocol: how AI apps plug into tools like this one. |
Way | Where it runs | On your phone | Cost | Guide |
1. Your computer (test) | Mac, Windows or Linux, read-only try-out | No | Free | |
2. Your own server | The same server as Coolify, in Docker, behind a Cloudflare tunnel | Yes, always on | Free (your server) |
The server version has a public address that Claude connects to, plus a Confirm page behind Zero Trust. A wrong Cloudflare setup could expose the Confirm page. Followsetup-own-server.md in order and stop if a check fails.
Not sure? Start with1: nothing leaves your computer except calls to your own Coolify and Cloudflare. Using an AI coding agent like Claude Code? AGENTS.md explains the project to it.
40 tools in two groups. All of them are listed in docs/tools.md.
Look (free, nothing changes)
Coolify: overview of apps, services and databases, one resource's details, environment variable names (never values), logs, deployments and their build logs, what looks unhealthy, servers, registries, volumes, scheduled tasks and backups.
Cloudflare: DNS records, rule sets, tunnels and their routes, Zero Trust apps, and a short list of other read-only paths.
Server (optional, over SSH): disk, memory, load and Docker space, and what a terminal shows.
This tool: its own status and its action log.
Change (each one is a ticket that needs your tap)
Coolify: deploy, start, stop or restart, cancel a deployment, set an environment variable, change one setting, roll back, clean up Docker, run a backup or a scheduled task.
Cloudflare: create, change or delete one DNS record, add, change or remove one tunnel route.
Terminal (optional): open one, type into it, close it.
This is the safe try-out on your computer, with read-only tokens. For the real thing on a server, see setup-own-server.md.
Install uv, then get the code:
git clone https://github.com/Self-hosted-MCP/Coolify-Cloudflare-MCP
cd Coolify-Cloudflare-MCP
uv syncMake a Coolify API token with only the read permission, and a Cloudflare token from the "Read all resources" template. Copy .env.example to .env and fill in the read-only values. docs/setup-computer.md shows each step.
Start it:
uv run python scripts/run-local-test.pyYou should see the server start on 127.0.0.1. It starts frozen, so nothing can change.
Connect your AI app. See docs/connect-your-ai.md.
Ask your AI app: "Give me an overview of my Coolify apps."
Guide | Read it when |
You want to try it, free, with read-only tokens | |
You want it always on, next to Coolify | |
It's running and you want to use it in your app | |
You want ideas | |
You want to know what the AI can do | |
You want to change how it behaves | |
Before you let an AI change anything | |
You want to take a change back, or back things up | |
You want to know what it protects against, and what not | |
You want to know what is kept and where | |
You want to know how it works inside | |
You want to see how much of the code the tests run | |
You want the newest version | |
You have a quick question | |
Something doesn't work | |
You want to know what's planned | |
You found a security problem | |
You want to know what changed in each version | |
You want to report a bug or send a fix | |
You want to see who helped, or be added | |
You want to know how decisions are made | |
You need help and don't know where to ask | |
You (or your AI coding agent) want to change the code or set it up | |
You want every setting in one file |
Creating and deleting apps, services and databases. Each type needs its own careful design. Use the Coolify dashboard.
Cloudflare changes outside DNS records and tunnel routes. Zero Trust, WAF and R2 changes can lock you out, so the Cloudflare dashboard is the right place.
Reload Compose. Coolify has no clear API call for it.
Traffic and security graphs. They use a different Cloudflare API.
Hosting-company one-click deploys and a Claude Desktop extension. The server needs a tunnel and Zero Trust, so these do not fit yet.
You want to | Go to |
Fix a problem yourself | |
Report a bug | |
Ask a question or share an idea | |
Report a security problem, privately |
Issues are public, so leave out passwords, keys and private data.
Thank you to everyone who helped. Code, bug reports, ideas, docs and design all count. See CONTRIBUTORS.md, and add yourself when you send a pull request.
Coolify-Cloudflare-MCP was made by Self-hosted-MCP. Coolify and Cloudflare are trademarks of their owners; this project isn't made by or affiliated with them.
You're welcome to use, fork, change and build on it under the Apache License 2.0 (Apache-2.0) and the notices in NOTICE. In short:
GitHub's "Cite this repository" button uses CITATION.cff.
Coolify-Cloudflare-MCP is free software you run yourself. It comes as is, with no warranty: you use it at your own risk, and no author is responsible for lost or damaged data, or for changes you confirm (the license says so in full). Keep a backup anyway.
Apache License 2.0 (Apache-2.0), with the notices in NOTICE. Copyright 2026 Self-hosted-MCP and Coolify-Cloudflare-MCP contributors.
This server cannot be deployed
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
AI agents propose database changes as reviewable requests — no direct write access.
Supervised API-write gateway for AI agents with policy, human approval and execution receipts.
Security gateway for AI agents: policy, approval, and audited execution, no secrets shared.
