Cloudflare
Consume Cloudflare API
About
Cloudflare ships in the w6w first-party pack. It declares 8 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.cloudflare- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- DevOps & Infrastructure
Overview
Cloudflare sits in front of a domain’s traffic, and this app reaches the parts of that surface a workflow is most likely to need: the zones (domains) a token can see, their settings and analytics, DNS records, and the edge cache in front of them.
List and inspect zones and their configuration, read request and bandwidth analytics over a time range, list, create and delete DNS records, and purge the cache — either everything or a specific list of URLs. A deploy workflow is the common trigger: update a DNS record, then purge the cache so the change takes effect immediately instead of waiting out the TTL.
DNS record creation covers the common record types that fit a single value field (A, AAAA, CNAME, MX, NS, TXT, SRV, CAA, PTR); types needing structured, record-specific fields are left out. Cache purge supports purge-everything and purge-by-URL-list, which work on every plan, rather than the tag/hostname/prefix purge that Cloudflare reserves for Enterprise.
Build with Cloudflare
Three routes to the same 8 actions. The Workflow tab is generated from Cloudflare's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Purge cache
cache-purge Purge everything, or purge a specific list of URLs, from a zone's edge cache
Get zone analytics
zone-analytics-get Get request, bandwidth, cache and threat totals for a zone over a time range
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Cloudflare's real ids.
{
"manifestVersion": "2",
"name": "cloudflare-example",
"steps": [
{
"id": "dns-record-create",
"uses": {
"app": "io.w6w.cloudflare",
"action": "dns-record-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"zoneId": "<zoneId>",
"type": "<type>",
"name": "<name>"
}
}
]
}Here are some of the things you can do
-
Create a DNS record
performdns-record-create -
List DNS records
readdns-record-list -
Get zone analytics
readzone-analytics-get -
Get a zone
readzone-get -
List zones
readzone-list
+3 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Cloudflare, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Cloudflare. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "dns-record-create",
payload: {
zoneId: "<value>",
type: "<value>",
name: "<value>",
content: "<value>",
// ttl: "<value>",
// proxied: "<value>",
// priority: "<value>",
// comment: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action dns-record-create --payload '{"zoneId":"<value>","type":"<value>","name":"<value>","content":"<value>"}'Give an AI agent Cloudflare — without giving it Cloudflare's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.cloudflare#dns-record-create",
"input": {
"zoneId": "<zoneId>",
"type": "<type>",
"name": "<name>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Cloudflare connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Cloudflare's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Cloudflare itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Cloudflare declares its own checks, so its health is a property of the app rather than something the host guesses at.
Cloudflare platform status
Atlassian Statuspage rollup for www.cloudflarestatus.com, with per-component detail. Unauthenticated and unsigned.
API rate-limit headroom
Requests remaining on this token, read off the `RateLimit`/`RateLimit-Policy` headers.