Cloudflare + Claude
How to connect Cloudflare to Claude
Connect Cloudflare to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
On this page
Overview
This guide connects Cloudflare to Claude through Agent200's MCP server. When you finish, Claude can search, read and act in Cloudflare with the tools Agent200 provides, whenever a request needs them.
You add one MCP server to Claude with your Agent200 API key. Your Cloudflare account is connected through managed OAuth: you approve access once on Cloudflare's own page, and Agent200 keeps the connection working.
- Connector
- Cloudflare
- Works with
- Claude ยท Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 6 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- Cloudflare enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Cloudflare account. They approve access once, on Cloudflare's own page.
- Claude, with custom MCP servers allowed. Custom connectors are on every Claude plan (Free: one). Sending an API key uses the Request headers option, a beta that only some accounts have; on Team and Enterprise an Owner adds the connector for everyone.
Connect Cloudflare to Claude
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Claude in the next step, as "Authorization: Bearer <your key>". One key covers Cloudflare and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Open Connectors in Claude
On a Free, Pro, Max or Ultra plan, go to Customize > Connectors. On Team or Enterprise, an Owner goes to Organization settings > Connectors; members then find the connector under Customize > Connectors.
-
3
Step 3: Add a custom connector
Select Add, then Add custom connector. Enter a name, Agent200, and the remote MCP server URL, then choose Continue.
-
4
Step 4: Send your key as a request header
Under Authentication choose No sign-in. Open Request headers, pick
authorization, enterBearerfollowed by a space and your key, mark it Required and choose Add. Claude sends the value exactly as typed.Add custom connectorMCP: Claude custom connector (URL and request header) Remote MCP server URL: https://api.agent200.com/mcp/ Authentication: No sign-in Request header name: authorization Value: Bearer YOUR_AGENT200_API_KEY -
5
Step 5: Turn it on in a chat
In a chat, select + > Connectors and turn Agent200 on. Ask Claude to list the Agent200 tools to check the connection; Claude asks before a tool runs the first time.
-
6
Step 6: Connect your Cloudflare account
The first time you ask Claude for something in Cloudflare, Agent200 returns an authorization link. Open it and approve access on Cloudflare's own page. Agent200 stores the connection and keeps it working; your password never reaches Claude or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
What are the DNS records for example.com
What should come back
- A result from that user's own Cloudflare account.
-
Behind the scenes, Claude calls
cloudflare_list_zones.
If you get an authorization link instead, the user has not connected Cloudflare yet. Show them the link, then run the request again.
Get your API key
Create a key in the Agent200 dashboard. It reaches Cloudflare and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect Cloudflare to Claude.
Goal: connect Cloudflare to Claude with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/cloudflare/framework/claude/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Claude's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure Cloudflare is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Claude: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Claude's exact menus or commands. 4. The first Cloudflare request returns an authorization link if the user has not connected Cloudflare yet: show it to them and continue once they have approved access on Cloudflare's own page. 5. Check it works with this request: "What are the DNS records for example.com" What should come back: - A result from that user's own Cloudflare account. - Behind the scenes, Claude calls `cloudflare_list_zones`. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Cloudflare, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/cloudflare/framework/claude.md
Cloudflare tools Claude can call
-
List zones
Readcloudflare_list_zonesList the domains in the user's account.
-
List DNS records
Readcloudflare_list_dns_recordsList the DNS records of a zone.
-
Create a DNS record
Writecloudflare_create_dns_recordAdd a DNS record to a zone.
-
Update a DNS record
Writecloudflare_update_dns_recordChange a DNS record's content or settings.
-
Delete a DNS record
Writecloudflare_delete_dns_recordRemove a DNS record from a zone.
-
Purge the cache
Writecloudflare_purge_cachePurge cached files for a zone, by URL or all of them.
No tool matches that search.
How it works
-
01
You ask Claude
In your own words, for something in Cloudflare.
-
02
Claude picks a tool
It sees the Cloudflare tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Cloudflare connection, within the tools and scopes your project allows.
-
04
Claude answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Cloudflare account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Cloudflare enforces what its API grants.
Troubleshooting
There is no Request headers section
Request headers are a Claude beta that only some accounts have. Without it, Claude cannot send an API key to a custom connector: use Claude Code, or the Agent200 SDK in your own agent.
Claude cannot reach the server
Check the header value is Bearer, a space, then your key, and that the URL is exactly the Agent200 MCP server address.
A Team or Enterprise member cannot add the connector
Only an Owner adds custom connectors, in Organization settings > Connectors. Members then connect it under Customize > Connectors.
You created a new API key
Claude does not let you edit a connector’s authentication. Remove the Agent200 connector and add it again with the new key.
Claude does not use the Cloudflare tools
Open + > Connectors in that chat and check Agent200 is on, and that no tool is set to Blocked under Customize > Connectors. Naming Cloudflare in the request also helps.
Claude shows a Cloudflare authorization link
You have not connected Cloudflare yet, or the connection needs to be approved again. Open the link, approve access on Cloudflare's own page, then ask Claude again.
A tool call is refused or returns less than expected
Agent200 runs only what your project allows. Check that Cloudflare and the tools you need are enabled in the dashboard's Connectors settings, and that you granted Cloudflare the access the task needs.
The API key was pasted into a chat or committed
Create a new key on the API keys page, replace it in Claude's MCP settings, and stop using the old one. Paste the key only into Claude's settings, never into a chat.
