Cloudflare connector for AI agents

Tools your DevOps agent reaches for on Cloudflare, scoped per user.

CALL ANY TOOL

Edge and DNS visibility in one toolkit: accounts, zones, DNS records, Worker scripts, and Zero Trust access apps. Each call uses the user's own OAuth token.

cloudflare_access_application_create

Create access application

Create a new Zero Trust Access application to protect a domain behind Cloudflare Access authentication policies.

Parameters

Name

Type

Required

Description

account_id

string

Required

The ID of the Cloudflare account

domain

string

Required

The domain (and optional path) this application protects

name

string

Required

Display name of the application

session_duration

string

Optional

How long an authenticated session stays valid before re-authentication is required

type

string

Optional

Type of Access application

cloudflare_access_application_delete

Delete access application

cloudflare_access_application_get

Get access application

cloudflare_access_application_list

List access application

cloudflare_account_list

List account

cloudflare_dns_record_create

Create dns record

cloudflare_dns_record_delete

Delete dns record

cloudflare_dns_record_get

Get dns record

cloudflare_dns_record_list

List dns record

cloudflare_dns_record_update

Update dns record

cloudflare_firewall_rule_create

Create firewall rule

cloudflare_firewall_rule_list

List firewall rule

cloudflare_load_balancer_create

Create load balancer

cloudflare_load_balancer_list

List load balancer

cloudflare_page_rule_create

Create page rule

cloudflare_page_rule_list

List page rule

cloudflare_pages_project_list

List pages project

cloudflare_ruleset_entrypoint_update

Update ruleset entrypoint

cloudflare_user_get

Get user

cloudflare_worker_route_create

Create worker route

cloudflare_worker_route_list

List worker route

cloudflare_worker_script_delete

Delete worker script

cloudflare_worker_script_get

Get worker script

cloudflare_worker_script_list

List worker script

cloudflare_zone_analytics_dashboard

Zone analytics dashboard

cloudflare_zone_create

Create zone

cloudflare_zone_get

Get zone

cloudflare_zone_purge_cache

Zone purge cache

cloudflare_zone_setting_get

Get zone setting

cloudflare_zone_setting_update

Update zone setting

For more tools, view docs.

Build your Agent

Drop the toolkit in, point it at the user, and your agent can audit zones and DNS from the first run.

import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["cloudflare"], toolNames: ["cloudflare_zone_list", "cloudflare_dns_record_list", "cloudflare_worker_script_list"] },
  pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  schema: z.object({}).passthrough(),
  func: async (args) => {
    const { data } = await sk.tools.executeTool({
      toolName: t.tool.definition.name,
      identifier: "user_123",
      params: args,
    });
    return JSON.stringify(data);
  },
}));

const agent = createReactAgent({ llm, tools: lcTools });

import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["cloudflare"], toolNames: ["cloudflare_zone_list", "cloudflare_dns_record_list", "cloudflare_worker_script_list"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  type: "function",
  function: {
    name: t.tool.definition.name,
    description: t.tool.definition.description,
    parameters: t.tool.definition.input_schema,
  },
}));

const resp = await openai.responses.create({
  model: "gpt-4o", input: prompt, tools: llmTools,
});

import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["cloudflare"], toolNames: ["cloudflare_zone_list", "cloudflare_dns_record_list", "cloudflare_worker_script_list"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
  model: "claude-sonnet-4-6", max_tokens: 1024,
  tools: llmTools,
  messages: [{ role: "user", content: prompt }],
});

import { Agent } from "@google/adk/agents";
import {
  MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
  connectionParams: new StreamableHTTPConnectionParams({
    url: "https://mcp.scalekit.com/cloudflare",
    headers: { Authorization: `Bearer ${userScopedToken}` },
  }),
});

const agent = new Agent({
  name: "agent", model: "gemini-2.0-flash",
  tools: await toolset.getTools(),
});

Try these prompts

Paste any prompt into your agent to start auditing Cloudflare DNS and edge config from your workflows.

DNS audits

Copy the prompt

Copied

List every A record on [zone] that is DNS only instead of proxied.

Copy the prompt

Copied

Find records across all zones still pointing at [old_ip].

Copy the prompt

Copied

Show TTLs for the MX records on [zone].

Edge inventory

Copy the prompt

Copied

List all Worker scripts in the account with their last modified date.

Copy the prompt

Copied

Which zones in this account are not on the active status?

Copy the prompt

Copied

Summarize the Zero Trust access applications and who they are scoped to.

Account review

Copy the prompt

Copied

Which Cloudflare accounts can I see and what plans are they on?

Copy the prompt

Copied

Show my current Cloudflare user profile and account memberships.

Copy the prompt

Copied

Group all zones by account and flag any without DNS records.

SEE HOW AUTH WORKS

Your users connect once. Their Cloudflare credentials stay vaulted, every call is scope-checked, and every action is logged.

Authorize

Your user connects

Cloudflare

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Cloudflare

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Cloudflare

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Cloudflare

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

Engineering Teams

DevOps assistant agent

Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.

Engineering Teams

Engineering standup agent

Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.

Engineering Teams

Auto release notes agent

Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.

Engineering Teams

Slack triage

Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.

// shared token
audit → bot_service_account
user_filter → broken

// scalekit
audit → user_abc
scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Cloudflare today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Cloudflare as the user or as a shared key?

As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Cloudflare OAuth token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Cloudflare?

Yes. Pass a tool name filter to listScopedTools so the DevOps agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Cloudflare.

What happens when a user revokes Cloudflare access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does the agent see every Cloudflare zone or only the user's?

Only what the authorizing user can see. Scalekit resolves that user's OAuth token at request time, so Cloudflare's own account and role membership decides the result set. An agent run by a member with one account never returns zones from another.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit