# How to connect Cloudflare to OpenClaw (paste one key, 20 tools) > Connect Cloudflare to OpenClaw with ClawLink: paste your Cloudflare key once and 20 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/cloudflare The usual route to Cloudflare access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Cloudflare setup: install one ClawHub skill, connect Cloudflare in the browser, and OpenClaw can call real Cloudflare actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. **Start here:** install the ClawLink plugin (`openclaw plugins install clawhub:clawlink-plugin`), pair it in the browser, then connect the app in the ClawLink dashboard. The interactive install prompt is on the web version of this page: https://claw-link.dev/openclaw/cloudflare ## Setup It takes three steps to connect OpenClaw to Cloudflare. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Cloudflare** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect cloudflare # connect Cloudflare (browser OAuth) npx -y @useclawlink/cli actions cloudflare # list available actions npx -y @useclawlink/cli run cloudflare --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Cloudflare in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Cloudflare API key once. Verify the connection by asking OpenClaw: > Create it in Cloudflare for me, then confirm the important fields before you finish. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Cloudflare is connected in the dashboard, that agent calls the same 20 Cloudflare tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Cloudflare MCP for OpenClaw Looking for a Cloudflare MCP server for OpenClaw? ClawLink connects Cloudflare to OpenClaw and exposes 20 Cloudflare tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Cloudflare integration](https://claw-link.dev/hermes/cloudflare) works the same way. ## What the OpenClaw Cloudflare integration can do 20 Cloudflare tools are ready for OpenClaw once the account is connected. The 17 below are the ones people reach for most; your agent can call all 20. ### 17 of 20 Cloudflare tools for OpenClaw | Tool | What it does | |---|---| | **Create dns record** `cloudflare_create_dns_record` | Tool to create a new DNS record within a specific zone. Requires write privileges and makes live changes to the zone. | | **Create list** `cloudflare_create_list` | Create a new empty custom list for use in WAF rules and filters. Lists can contain IP addresses, hostnames, ASNs, or redirects. Once created, use separate actions to add items to the list. | | **Create zone** `cloudflare_create_zone` | Creates a new DNS zone (domain) in Cloudflare. A zone represents a domain and its DNS records. Use this when adding a new domain to manage with Cloudflare. | | **Get bot management settings** `cloudflare_get_bot_management_settings` | Tool to retrieve a zone's Bot Management configuration (Bot Fight Mode / Super Bot Fight Mode / Enterprise Bot Management). Use after identifying the correct zone_id (e.g., via CLOUDFLARE_LIST_ZONES). | | **Get lists** `cloudflare_get_lists` | Tool to fetch all WAF lists (no items) for an account. Results are paginated; iterate using page and per_page parameters until result_info.total_pages is reached to retrieve all lists. | | **List account members** `cloudflare_list_account_members` | Lists all members of a Cloudflare account with their roles, permissions, and status. | | **List accounts** `cloudflare_list_accounts` | List all Cloudflare accounts you have ownership or verified access to. Retrieves a paginated list of accounts with their details including account ID, name, type, settings, and creation date. | | **List dns records** `cloudflare_list_dns_records` | Tool to list and search DNS records in a Cloudflare zone. | | **List firewall rules** `cloudflare_list_firewall_rules` | Tool to list firewall rules for a specific DNS zone. Use after confirming the zone ID to retrieve and audit current firewall rules. Does not expose Workers routes or other routing constructs. | | **List monitors** `cloudflare_list_monitors` | List all load-balancer monitors in a Cloudflare account | | **List pools** `cloudflare_list_pools` | List all load balancer pools in a Cloudflare account | | **List tunnels** `cloudflare_list_tunnels` | List Cloudflare Tunnel (cloudflared) tunnels in an account to discover tunnel IDs, names, and | | **List zones** `cloudflare_list_zones` | Lists, searches, sorts, and filters zones in the authenticated account | | **Update dns record** `cloudflare_update_dns_record` | Update an existing DNS record within a specific zone | | **Update list** `cloudflare_update_list` | Update the description of a WAF list (cannot update items) | | **Update tunnel configuration** `cloudflare_update_tunnel_configuration` | Update a remotely-managed Cloudflare Tunnel's configuration (ingress rules and routing) | | **Update zone** `cloudflare_update_zone` | Update properties of an existing zone; changes apply immediately to the live zone | ## Example prompts **Create Dns Record** > Create it in Cloudflare for me, then confirm the important fields before you finish. **Create List** > Create it in Cloudflare for me, then confirm the important fields before you finish. **Create Zone** > Create it in Cloudflare for me, then confirm the important fields before you finish. **Get Bot Management Settings** > Pull the relevant data from Cloudflare, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Cloudflare working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Cloudflare API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Cloudflare account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Cloudflare. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Cloudflare actions to the runtime in a format your agent can reliably use. | 20 tools for Cloudflare are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Cloudflare to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Cloudflare in the browser, and the 20 tools above work from chat. There is no SDK and no config file, and the Cloudflare key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Cloudflare skill but can't call the tools The ClawHub skill teaches OpenClaw about Cloudflare, but the calls run through the ClawLink plugin and your connected account. Make sure Cloudflare is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Cloudflare from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Cloudflare tools Cloudflare tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Cloudflare call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Cloudflare returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Cloudflare has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Cloudflare integration? Yes. ClawLink is the fastest way to connect OpenClaw to Cloudflare: link your Cloudflare account once in the browser and OpenClaw can call the Cloudflare API through 20 ready-made tools — no custom code or token handling. ### How do I add Cloudflare to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Cloudflare skill from ClawHub, then you click Connect in the dashboard to authorize Cloudflare. OpenClaw calls the tools from the next message — no config files, and the Cloudflare key you paste is stored server-side instead of in your environment. ### How long does it take to connect Cloudflare to OpenClaw? About two minutes. Sign in, click Connect next to Cloudflare in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Cloudflare up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Cloudflare working from chat. ### OpenClaw installed the Cloudflare skill but can't call the tools The ClawHub skill teaches OpenClaw about Cloudflare, but the calls run through the ClawLink plugin and your connected account. Make sure Cloudflare is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [GitHub tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [OpenClaw PagerDuty integration](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [OpenClaw SafetyCulture integration](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.