Manage Your Cloudflare DNS, Cache, and Traffic Through Your Muse

Through an AnythingMCP custom connector, your muse can look after your Cloudflare websites from a chat: read and change DNS records, clear cached pages, check traffic, and list Workers and buckets.

What it does

The connector adds 26 tools. For DNS it can list and read records, export them all as a backup, and create or change a record, showing old and new values before it acts. For the cache it can clear up to 100 named pages, tags, or hosts at once. It reads zone settings such as HTTPS and security level, your redirect, transform, and cache rules plus older page rules, and reports daily traffic with requests, data served, threats, page views, and visitors, by status code and country. It also lists Workers, their routes and domains, and R2 buckets, and reads Worker settings without showing secret values. Two tools start switched off: deleting a DNS record and clearing the whole cache.

How to use it

1. Start an AnythingMCP account and add the Cloudflare connector.
2. In the Cloudflare dashboard, open My Profile, then API Tokens, and create a custom token. Give it read access to zones, settings, rules, and analytics, plus DNS edit and cache purge only if you want changes. Limit it to one domain.
3. Copy the token, shown once, and paste it into the connector. Do not use the Global API Key.
4. In Muse, open Settings, then Connectors, and add a custom connector with the MCP server address AnythingMCP gives you. Sign in and approve.
5. Start with a read: ask which domains the token can see, then export DNS records as a backup before any change.

What you need

• A Muse account that can add custom connectors
• An AnythingMCP account with the Cloudflare connector added
• A Cloudflare account and an API token scoped to the domains you choose

What to watch for

• DNS changes go live within seconds. A wrong record can take a website or its email down, so check old and new values before you approve.
• Clearing the whole cache sends every visitor to your own server, which can overload a busy site. Clearing named pages usually suffices.
• A read-only setup works: give DNS read access only, leave out cache purge, and the muse can only report and advise.
• Traffic history depends on your plan; the free plan covers recent weeks.
• The connector does not edit rule sets or settings, handle certificates, deploy Workers, or touch billing or registration. Meta does not review custom connectors. The muse prepares, you decide.