# How to connect Cloudflare to Grok Bot (paste one key, 20 tools) > Connect Cloudflare to Grok Bot 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/grokbot/cloudflare Grok Bot runs on its own cloud computer, so most Cloudflare guides send you to register an OAuth app and paste keys into a sandbox that resets. ClawLink gives Grok Bot a more practical Cloudflare setup: it runs one CLI command, you approve once in the browser, and Grok Bot can call real Cloudflare actions from chat with no auth, token refresh, or tool wiring to build yourself. **Start here — paste this into Grok Bot to set up ClawLink:** > Set up ClawLink for me and tell me when it's ready. > 1. Pair this machine. It prints an approval link, so show me the link and stop, don't wait: `npx -y @useclawlink/cli login` > 2. I'll approve it in my browser, then reply "approved". > 3. When I say approved, connect the app: `npx -y @useclawlink/cli connect cloudflare` > 4. Then run `npx -y @useclawlink/cli whoami` and tell me whether ClawLink is ready. ## Setup It takes three steps to connect Grok Bot to Cloudflare. 1. **Pair from the terminal** — ask Grok Bot to run `npx -y @useclawlink/cli login` and approve the link it prints. 2. **Connect Cloudflare** — `npx -y @useclawlink/cli connect cloudflare`, then approve in the browser. 3. **Use it from chat** — ask Grok Bot in plain English. **The same CLI works from any agent with shell access:** ```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 prompt above does all of this. By hand, it is two commands Grok Bot runs in its own terminal, and one browser approval: ```bash npx -y @useclawlink/cli login # prints an approval link, approve it in your browser npx -y @useclawlink/cli connect cloudflare ``` Pair once and it sticks: the key is written to ~/.clawlink/credentials.json inside Grok Bot's sandbox, so it survives between sessions. Prefer native tools over shell commands? Add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. Same account, no CLI. Verify the connection by asking Grok Bot: > Create it in Cloudflare for me, then confirm the important fields before you finish. ### Using a different agent? The CLI above is not specific to Grok Bot. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account the same way: ```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 Grok Bot Looking for a Cloudflare MCP server for Grok Bot? ClawLink connects Cloudflare to Grok Bot 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 a different agent? The [OpenClaw Cloudflare integration](https://claw-link.dev/openclaw/cloudflare) and the [Hermes Cloudflare integration](https://claw-link.dev/hermes/cloudflare) connect the same ClawLink account the same way. ## What the Grok Bot Cloudflare integration can do 20 Cloudflare tools are ready for Grok Bot 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 Grok Bot | 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 Grok Bot. 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 Grok Bot 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. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ### 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 Grok Bot Cloudflare integration? Yes. ClawLink is the fastest way to connect Grok Bot to Cloudflare: link your Cloudflare account once in the browser and Grok Bot can call the Cloudflare API through 20 ready-made tools — no custom code or token handling. ### How do I connect Cloudflare to Grok Bot with ClawLink? Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal and approve the link it prints, then `npx -y @useclawlink/cli connect cloudflare` to authorize Cloudflare. Grok Bot calls the tools from the next message, and the pairing persists in its sandbox, so this is a one-time step: 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 Grok Bot? About two minutes. Sign in, click Connect next to Cloudflare in the dashboard, authenticate, and Grok Bot 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 Grok Bot. That is fine if you want to build and maintain the integration yourself. Most teams just want Cloudflare working from chat. ### Grok Bot says it cannot add ClawLink as an MCP server Grok Bot only attaches MCP servers that are reachable over the public internet, so a local stdio server is refused. You do not need one. Ask Grok Bot to run `npx -y @useclawlink/cli login` in its terminal instead. The CLI is a shell command, not an MCP server. If you would rather have native tools, add `https://claw-link.dev/api/mcp` as a custom connector at grok.com/connectors and approve the ClawLink sign-in. ## Related - [Connect GitHub](https://claw-link.dev/grokbot/github) — Manage repositories, issues, pull requests, and workflows - [Grok Bot PagerDuty integration](https://claw-link.dev/grokbot/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/grokbot/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.