# How to connect Cloudflare Api Key to OpenClaw (paste one key, 25 tools) > Connect Cloudflare Api Key to OpenClaw with ClawLink: paste your Cloudflare Api Key key once and 25 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/cloudflare-api-key The usual route to Cloudflare Api Key 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 Api Key setup: install one ClawHub skill, connect Cloudflare Api Key in the browser, and OpenClaw can call real Cloudflare Api Key actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Cloudflare Api Key. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Cloudflare Api Key** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **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-api-key # connect Cloudflare Api Key (browser OAuth) npx -y @useclawlink/cli actions cloudflare-api-key # list available actions npx -y @useclawlink/cli run cloudflare-api-key --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 Api Key in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Cloudflare Api Key API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Cloudflare Api Key, summarize it in plain English, and point out anything that needs attention. ### 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 Api Key is connected in the dashboard, that agent calls the same 25 Cloudflare Api Key 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 Api Key MCP for OpenClaw Looking for a Cloudflare Api Key MCP server for OpenClaw? ClawLink connects Cloudflare Api Key to OpenClaw and exposes 25 Cloudflare Api Key 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 Api Key integration](https://claw-link.dev/hermes/cloudflare-api-key) works the same way. ## What the OpenClaw Cloudflare Api Key integration can do 25 Cloudflare Api Key tools are ready for OpenClaw once the account is connected. The 20 below are the ones people reach for most; your agent can call all 25. ### 20 of 25 Cloudflare Api Key tools for OpenClaw | Tool | What it does | |---|---| | **Get cloudflare ip addresses** `cloudflare_api_key_get_cloudflare_ip_addresses` | Retrieve IP addresses used on the Cloudflare or JD Cloud network | | **Get entrypoint ruleset version** `cloudflare_api_key_get_entrypoint_ruleset_version` | Retrieves a specific historical version of an entry point ruleset from Cloudflare | | **Get lockdown rule** `cloudflare_api_key_get_lockdown_rule` | Get a Zone Lockdown rule | | **Get regional tiered cache** `cloudflare_api_key_get_regional_tiered_cache` | Get the regional tiered cache setting for a zone | | **Get ruleset** `cloudflare_api_key_get_ruleset` | Fetch the latest version of a ruleset by ID | | **Get zone details** `cloudflare_api_key_get_zone_details` | Get details for a specific zone | | **List dns records** `cloudflare_api_key_list_dns_records` | List, search, sort, and filter DNS records for a Cloudflare zone | | **List zones** `cloudflare_api_key_list_zones` | List, search, sort, and filter Cloudflare zones | | **Create dns record** `cloudflare_api_key_create_dns_record` | Create a new DNS record in a Cloudflare zone | | **Create lockdown rule** `cloudflare_api_key_create_lockdown_rule` | Create a Zone Lockdown rule | | **Create rule in ruleset** `cloudflare_api_key_create_rule_in_ruleset` | Add a rule to an existing ruleset | | **Create ruleset** `cloudflare_api_key_create_ruleset` | Creates a new Cloudflare ruleset at account or zone scope | | **Overwrite dns record** `cloudflare_api_key_overwrite_dns_record` | Completely overwrite a DNS record | | **Rerun zone activation check** `cloudflare_api_key_rerun_zone_activation_check` | Triggers a new activation check for a zone with 'pending' status | | **Update dnssec status** `cloudflare_api_key_update_dnssec_status` | Update DNSSEC configuration for a zone | | **Update lockdown rule** `cloudflare_api_key_update_lockdown_rule` | Update a zone lockdown rule | | **Update rule in ruleset** `cloudflare_api_key_update_rule_in_ruleset` | Update a specific rule in a ruleset | | **Update ruleset** `cloudflare_api_key_update_ruleset` | Update a Cloudflare ruleset, creating a new version | | **Update zone** `cloudflare_api_key_update_zone` | Edit a Cloudflare zone | | **Upload file to s3** `cloudflare_api_key_upload_file_to_s3` | Upload arbitrary file content to temporary storage | ## Example prompts **Get Cloudflare Ip Addresses** > Pull the relevant data from Cloudflare Api Key, summarize it in plain English, and point out anything that needs attention. **Get Entrypoint Ruleset Version** > Pull the relevant data from Cloudflare Api Key, summarize it in plain English, and point out anything that needs attention. **Get Lockdown Rule** > Pull the relevant data from Cloudflare Api Key, summarize it in plain English, and point out anything that needs attention. **Get Regional Tiered Cache** > Pull the relevant data from Cloudflare Api Key, 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 Api Key working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Cloudflare Api Key API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Cloudflare Api Key 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 Api Key. | 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 Api Key actions to the runtime in a format your agent can reliably use. | 25 tools for Cloudflare Api Key are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Cloudflare Api Key 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 Api Key in the browser, and the 25 tools above work from chat. There is no SDK and no config file, and the Cloudflare Api Key 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 Api Key skill but can't call the tools The ClawHub skill teaches OpenClaw about Cloudflare Api Key, but the calls run through the ClawLink plugin and your connected account. Make sure Cloudflare Api Key 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 Api Key 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 Api Key tools Cloudflare Api Key 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 Api Key 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 Api Key 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 Api Key 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 Api Key integration? Yes. ClawLink is the fastest way to connect OpenClaw to Cloudflare Api Key: link your Cloudflare Api Key account once in the browser and OpenClaw can call the Cloudflare Api Key API through 25 ready-made tools — no custom code or token handling. ### How do I add Cloudflare Api Key to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Cloudflare Api Key skill from ClawHub, then you click Connect in the dashboard to authorize Cloudflare Api Key. OpenClaw calls the tools from the next message — no config files, and the Cloudflare Api Key key you paste is stored server-side instead of in your environment. ### How long does it take to connect Cloudflare Api Key to OpenClaw? About two minutes. Sign in, click Connect next to Cloudflare Api Key in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Cloudflare Api Key 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 Api Key working from chat. ### OpenClaw installed the Cloudflare Api Key skill but can't call the tools The ClawHub skill teaches OpenClaw about Cloudflare Api Key, but the calls run through the ClawLink plugin and your connected account. Make sure Cloudflare Api Key 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 - [Connect GitHub](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](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.