Cloudflare MCP server
Inspect zones and DNS records with Arc0’s Cloudflare tools. Approved writes can change live DNS or purge cached URLs, so each operation names the account and target explicitly. Connect through Arc0 to use the actions your identity is allowed to call.
Working with Cloudflare
For a DNS change, begin with cloudflare.list_zones in the configured account and cloudflare.list_dns_records for the chosen zone. Record-name matching is exact and case-insensitive. Continue through pages when necessary rather than assuming that the first page contains every record. cloudflare.get_dns_record reads a known record before editing it.
cloudflare.create_dns_record supports approved A, AAAA, CNAME, and TXT records. cloudflare.update_dns_record changes an existing record and can redirect live traffic; cloudflare.delete_dns_record removes it. Confirm the zone, record ID, and desired content before either operation. If creation loses its response, list matching records before retrying, because another request can create a duplicate.
cloudflare.purge_cache_urls evicts the selected URLs from cache tiers. Acceptance does not prove eviction has completed, and cached content may become unavailable if the origin is down. cloudflare.list_workers_scripts provides an account inventory of Worker metadata, not source code or deployment control. cloudflare.verify_token checks a user-owned token’s status but does not by itself prove access to a particular zone.
Official MCP reference: Cloudflare documentation.
Agent workflows for Cloudflare.
Review a zone’s DNS
Use cloudflare.list_zones and cloudflare.list_dns_records to locate the exact record before proposing a change.
Add a reviewed record
Use cloudflare.create_dns_record for an approved A, AAAA, CNAME, or TXT record.
Verify a DNS update
Use cloudflare.get_dns_record before and after cloudflare.update_dns_record to compare the intended fields.
Inspect deployed Workers
Use cloudflare.list_workers_scripts for Worker metadata without fetching code, secrets, or bindings.
9 Cloudflare actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
5Look things up, subject to your permissions.
- cloudflare.verify_tokenVerify token
Use when checking a user-owned API token status without exposing its value. Do not use for account-owned tokens or to prove access to a specific zone; those need separate checks.
- cloudflare.list_zonesList zones
Use when finding zone IDs in the configured account before DNS or cache operations. Follow result_info.total_pages. Do not use to inventory other accounts; use their own connection.
- cloudflare.list_dns_recordsList dns records
Use when inspecting DNS in the configured account or reconciling an uncertain create. Name matching is exact and case-insensitive. Follow result_info.total_pages. Do not use for fuzzy search or assume this page contains all records.
- cloudflare.get_dns_recordGet dns record
Use when reading a known DNS record in the configured account or verifying an uncertain write. Do not use without its record ID; list DNS records first.
- cloudflare.list_workers_scriptsList workers scripts
Use when inventorying Worker metadata in the configured account; accountId must match the connection. Do not use to fetch source code, bindings or secrets, or to deploy a Worker.
write
2Create and change things. Allow, or ask the user first.
- cloudflare.create_dns_recordCreate dns record
Use when adding an approved A, AAAA, CNAME or TXT record in the configured account. Changes live DNS. Do not use for unapproved targets or updates. After a timeout, list matching records before retrying; creation has no idempotency key.
- cloudflare.update_dns_recordUpdate dns record
Use when changing an approved DNS record in the configured account. Name/content changes can redirect live traffic. Do not use to create records or for unapproved targets. Read first; after an uncertain outcome read again before retrying.
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- cloudflare.delete_dns_recordDelete dns record
Use when removing an explicitly approved DNS record in the configured account. This can interrupt live traffic. Do not use to edit a record. Confirm zone and ID; after a timeout read it before retrying deletion.
- cloudflare.purge_cache_urlsPurge cache urls
Use when approved URLs must be evicted from every cache tier. Destructive: cached content is unavailable even if origin is down. Do not use for revalidation; prefer invalidate_cache (not exposed here). Acceptance is not proof of eviction; check cache status before retrying.
Control access to Cloudflare.
Connect the intended Cloudflare account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- cloudflare.create_dns_record: require approval
- cloudflare.delete_dns_record: deny
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Cloudflare connects.
Connect Cloudflare using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Cloudflare with your AI client.
Sign in to Arc0 and connect Cloudflare in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Cloudflare with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingCloudflare with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingCloudflare with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingCloudflare with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingCloudflare with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingCloudflare with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
More security and identity apps.
Cloudflare and Arc0, answered.
Is there an official Cloudflare MCP server, and how does Arc0 differ?
Yes. Cloudflare publishes its own MCP servers. Arc0’s current tools use the REST API for a defined DNS, cache, and Worker-metadata action set with an account-bound connection.
Which permissions does Arc0 need for Cloudflare?
Use a user-owned API token. Depending on the tools, permissions include Zone Zone Read, DNS Read, DNS Write, Cache Purge and Workers Scripts Read, restricted to intended resources. Account-owned tokens and global API keys are not this lane.
Does this work with Claude, ChatGPT, Codex and Cursor?
Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.
How are credentials stored, refreshed and revoked?
Arc0 stores the token encrypted and does not refresh it. Disconnect removes local access. Revoke the token in Cloudflare to invalidate it at the source; a replacement token has a new token identity.
What happens with rate limits or errors?
Cloudflare applies API and operation-specific limits. Arc0 reports rate-limit and permission failures. Read DNS after an uncertain write before retrying; cache-purge acceptance is not confirmation that every cached copy has been removed.
What is the availability of these Cloudflare tools?
These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.
Plug Cloudflare into your agent.
Cloudflare MCP server: 9 actions including verify token, list zones, list dns records. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Cloudflare and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Cloudflare.