Claude Cloudflare Developer Platform connectorWhat Claude can do in your Cloudflare Developer Platform account.
The Claude Cloudflare Developer Platform connector exposes 24 tools. 12 of them read your Workers and storage resources, 10 create, edit or delete resources, and 2 are documented nowhere. Below: what Claude can inspect, what it can remove, and what Cloudflare leaves unsaid.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for the person who runs a Cloudflare account
Checking what lives in a Cloudflare account normally means clicking through the dashboard product by product. With the connector, you ask Claude: it lists your Workers, your KV namespaces (key-value stores), your R2 buckets (file storage) and D1 databases, reads their details and can create or delete one when you ask.
Audit an account in one question. workers_list, kv_namespaces_list, r2_buckets_list and d1_databases_list give Claude the inventory, so it can tell you what exists and what looks forgotten.
Read the code behind a Worker. workers_get_worker_code returns a Worker's source code, which lets Claude explain what it does before anyone touches it.
Set up storage on request. For a new project, d1_database_create adds a database and kv_namespace_create a namespace; d1_database_query then runs a query against D1.
Now what the connector does not do. It covers the resources Cloudflare connects to a Worker through bindings, not your whole Cloudflare account: no tool here deploys a Worker according to the publisher's list. Cloudflare calls the server a work in progress. And the two account tools at the top of the list are described nowhere. For a no-code comparison on the storage side, see the Claude airtable connector.
The vocabulary in one minute
Five words you will meet while plugging Cloudflare Developer Platform into Claude.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while answering you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory lists each by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude its access. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown right in the chat.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service.
Plug Cloudflare Developer Platform into Claude in three steps
- 01
Find Cloudflare Developer Platform in Claude
In Claude's settings, open Customize, then Connectors, and look for Cloudflare Developer Platform in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first so each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Cloudflare Developer Platform in the window that Cloudflare Developer Platform opens itself. If the link ever breaks later on, use Disconnect and then plug it back in.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to Cloudflare Developer Platform, not to Claude, and it is what decides what the access covers. You can also withdraw that access later from your Cloudflare Developer Platform account.
The 24 tools, sorted by what they do
Cloudflare Developer Platform gives Claude 24 tools: 12 that read your account, 10 that change something in it, and 2 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes. Tool names stay exactly as Claude shows them.
- 12 read
- 10 write
- 2 not documented
What Claude reads (12)
12 toolsTwelve tools that list, inspect or query resources without altering them.
kv_namespaces_list
Lists every KV namespace in your Cloudflare account, the key-value stores Workers read from, so Claude sees what storage already exists.
kv_namespace_get
Returns the details of a single KV namespace, so Claude can confirm it is the one you mean before any other step.
workers_list
Lists all the Workers in your Cloudflare account, which gives Claude the starting map of what code runs there.
workers_get_worker
Gets the details of one Cloudflare Worker, useful to check a Worker before digging into its code.
workers_get_worker_code
Retrieves the source code of a Worker, so Claude can read it and explain in plain words what it does.
r2_buckets_list
Lists the R2 buckets in your account, the file storage spaces, giving Claude an overview of where objects are kept.
r2_bucket_get
Gets information about one specific R2 bucket, so Claude can describe it before you decide anything.
d1_databases_list
Returns every D1 database in your Cloudflare account, meaning the SQL databases your Workers rely on, so Claude can map them.
d1_database_get
Returns a given D1 database from your account, which Claude uses to confirm details before running anything against it.
d1_database_query
Runs a query against a D1 database in your account and brings the result back into the conversation.
hyperdrive_configs_list
Shows the Hyperdrive configurations in your account, the settings that connect Workers to an outside database, so dependencies become visible.
hyperdrive_config_get
Reads one specific Hyperdrive configuration, so Claude can show you its settings before you decide anything.
What Claude changes (10)
10 toolsTen tools that create, edit or delete resources in your account. No source spells out their confirmation, so the general rule below applies.
kv_namespace_create
Approval: see the ruleCreates a new KV namespace in your Cloudflare account, ready for a Worker to use.
kv_namespace_delete
Approval: see the ruleDeletes a KV namespace from your Cloudflare account, the way Cloudflare's one-line description puts it.
kv_namespace_delete; the general approvals rule covers it.kv_namespace_update
Approval: see the ruleUpdates the title of a KV namespace, the only change Cloudflare's list describes for this tool.
r2_bucket_create
Approval: see the ruleOpens a fresh R2 bucket in your Cloudflare account, an empty space ready to hold files for a project.
r2_bucket_delete
Approval: see the ruleDeletes an R2 bucket from your account, which removes that storage space.
d1_database_create
Approval: see the ruleSets up a new D1 database in your Cloudflare account, empty and ready for tables.
d1_database_delete
Approval: see the ruleDeletes a D1 database from your account, with everything the database contained.
hyperdrive_config_create
Approval: see the ruleAdds a Hyperdrive configuration so your Workers can reach an outside database.
hyperdrive_config_create; the general approvals rule covers it.hyperdrive_config_delete
Approval: see the ruleDeletes a Hyperdrive configuration from your account, cutting the link it provided between your Workers and that database.
hyperdrive_config_edit
Approval: see the rulePatches an existing Hyperdrive configuration, for example its cache settings, without recreating it.
Not documented (2)
2 toolsThe directory publishes these two names and nothing else. No official text says what they do, and this page will not guess from a name.
accounts_list
The directory lists this name, but Cloudflare's tool table for this server leaves it out and no Claude page mentions it. No source describes it, so this page stays silent on its role.
set_active_account
Only its name appears on the directory sheet. Cloudflare's README does not include it in the list of tools, and no official text explains it, so nothing is said here about what it affects.
What Claude asks before it acts
By default, Claude stops and asks you before any action it takes on an account on your behalf. The request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organization, for instance keeping reading open and closing writing. That setting applies to everyone and nobody gets around it from their own account. Finally, Claude works with your rights and nothing beyond: a resource your Cloudflare role cannot reach stays out of its reach too.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere, and that is a real hole in the catalog rather than a gap in our reading.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each sign in. For the live state of this one, go to Cloudflare Developer Platform's sheet in the official directory, the only place that shows it.
Where the Claude Cloudflare Developer Platform connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a Worker errors or a bucket fills up.
This connector is documented only by its publisher: neither Claude's help center nor Anthropic's developer docs cover it, and the documentation link on its sheet leads to Cloudflare's general support home. The facts here come from the directory sheet and the server's README on GitHub. The partner badge is not a security audit, and Anthropic states on every sheet that it does not control which tools a publisher exposes. The Integrations hub gathers the automation families.
Need help connecting Cloudflare Developer Platform to Claude?
A person reads every message.
