Connect your own Cloudflare account and Manus can check and update DNS records, read Workers and Pages deploys and logs, list your R2, KV and D1 storage, explain firewall and Zero Trust rules and turn traffic data into reports. For changes, ask for the list first and confirm it in the chat.
Check and change your Cloudflare DNS settings in plain words, without clicking through the dashboard record by record.
Tell Manus what the records are for. As your Cloudflare DNS AI helper, it lists the current records, writes the CNAME, MX or TXT records you need and checks them against what’s already there. Ask for the change list first and confirm it before anything is applied.
Manus compares your DNS records and proxy settings with what the site or mail service expects, then explains the likely cause and the fix in plain words.
Find out what changed in the latest deploy and why requests started failing, without digging through the dashboard.
Manus lists the recent deployments, reads the logs and points to the error and the change behind it. If the fix is in your code, connect GitHub too and it can open a pull request.
Version 7c41e9a removed the EXPORTS R2 binding, so env.EXPORTS is undefined when /orders/export saves the file. Add the binding back in wrangler.jsonc and deploy again.
Open the fix as a pull request with GitHubSee everything your account stores in one place, and which items nothing uses anymore.
Through the Cloudflare API MCP server, Manus lists your R2 buckets, KV namespaces and D1 databases with their size, and checks which Workers are bound to each one.
Get your security rules explained in plain words, and a weekly look at requests, cache and what was blocked.
Manus reads your WAF custom rules, rate limiting rules and Access policies, explains each one in a sentence and points out the ones that look broader than needed. Ask for suggestions only, and decide yourself what to change.
Manus pulls requests, cache use and blocked traffic for the last 7 days and writes a short report with a chart. To get it every week, set it up as a scheduled task.
There’s no Cloudflare MCP server setup to do and no API token to paste. Cloudflare is already in Manus Connectors, and you approve access on Cloudflare’s own screen.
In Manus, open Connectors and select Cloudflare.
Choose the accounts Manus can use. To limit what it can change, select Edit Permissions, then Read only.
Name a domain, Worker or bucket and say what you need in plain words.
Yes. Manus connects to Cloudflare’s official MCP (Model Context Protocol) server at mcp.cloudflare.com. This Cloudflare API MCP server covers the whole Cloudflare API and its developer docs. It’s already in Manus Connectors, so there’s nothing to install or host.
Open Connectors in Manus, select Cloudflare and sign in. On Cloudflare’s screen, choose the accounts Manus can use, review the permissions and select Authorize. This Cloudflare MCP server OAuth sign-in means your Cloudflare password is never shared with Manus.
Yes. When you sign in, select Edit Permissions on Cloudflare’s screen, then Read only. That turns off the optional edit permissions, and only the permissions Cloudflare marks as required stay on. If a task later needs a permission you left out, connect again and grant it.
DNS records, Workers, KV, R2, D1, Pages, firewall rules, Zero Trust, analytics and more, plus a search of Cloudflare’s developer docs. What it can do in each one depends on the permissions you grant.
Yes. Manus edits the record in your Cloudflare account through Cloudflare’s API, just like an edit in the dashboard, so there’s no separate publish step. Visitors may still see the old value for a few minutes while DNS caches update: Proxied records use a five-minute TTL, and DNS only records use the TTL you set. That’s why it’s worth reading the change list before you say OK.
Yes, for Workers that have Workers Logs turned on, which new Workers have by default. It can also read the build logs of Pages deployments. Name the Worker or project and say what went wrong.
No. Cloudflare’s server also accepts an API token, which suits scripts and CI/CD. In Manus, you sign in with your Cloudflare account and approve access on Cloudflare’s screen, so there’s no token to create or paste.
It’s how Cloudflare’s server covers more than 2,500 API endpoints with a few tools. Instead of one tool per endpoint, the agent finds the right endpoint with search, calls it with execute and looks things up with docs. The code it writes runs in an isolated sandbox on Cloudflare. There’s nothing to turn on in Manus.
No. A “Cloudflare MCP Claude Code” guide or a “Cloudflare MCP Codex” setup has you add Cloudflare’s server to that tool yourself. In Manus, Cloudflare is already in Connectors: sign in once, ask in a chat and the task runs in the cloud.
Manus is a general AI agent that works on your own Cloudflare account through Cloudflare’s official MCP server, with the permissions you grant. It isn’t a Cloudflare product. If you’re looking to build a Cloudflare Workers AI agent of your own, Workers AI and the Agents SDK are made for that, and Manus can still check the Workers you deploy.
No. Searches for Cloudflare MCP servers or a Cloudflare MCP gateway are often about building, hosting or securing your own MCP servers on Cloudflare. This page is about connecting your Cloudflare account to Manus, so you can work with your DNS, Workers, storage and security settings in a chat.
Yes. Open Connectors in Manus, select Cloudflare and choose Disconnect. You can also revoke it in your Cloudflare profile under Manage OAuth authorizations.