Skip to main content
toolsSource-backedReview first Safety · Privacy ·
Cloudflare logo

Cloudflare Agents SDK

Cloudflare framework for building, deploying, and running AI agents on Workers with durable platform primitives.

by Cloudflare·added 2026-04-27·
HarnessCLI
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://developers.cloudflare.com/agents/, https://github.com/cloudflare/agents
Brand
Cloudflare
Brand domain
developers.cloudflare.com
Brand asset source
brandfetch
Author
Cloudflare
Claim status
unclaimed
Last verified
2026-04-27

Schema details

Install type
copy
Troubleshooting
No
Source repository stats
Scope
Source repo
Tool listing metadata
Pricing
freemium
Disclosure
editorial
Application category
DeveloperApplication
Operating system
Web
Full copyable content
## Editorial notes

Cloudflare Agents SDK is relevant for teams that want agent runtimes close to edge compute, durable objects, and serverless deployment.

## Disclosure

Editorial listing. No paid placement or affiliate link is used.

About this resource

Editorial notes

Cloudflare Agents SDK is relevant for teams that want agent runtimes close to edge compute, durable objects, and serverless deployment.

Disclosure

Editorial listing. No paid placement or affiliate link is used.

Source citations

Add this badge to your README

Show that Cloudflare Agents SDK is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/tools/cloudflare-agents-sdk.svg)](https://heyclau.de/entry/tools/cloudflare-agents-sdk)

How it compares

Cloudflare Agents SDK side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

Field

Cloudflare framework for building, deploying, and running AI agents on Workers with durable platform primitives.

Open dossier

A source-backed Cloudflare collection for building AI apps on the edge: combine Workers, Workers AI, Agents, D1, KV, R2, Wrangler deployment operations, and Cloudflare MCP access with explicit environment and data boundaries.

Open dossier

A practical architecture guide for building AI agents on Cloudflare Workers with Workers AI inference and durable per-agent state. Use the Agents API, Durable Objects, bindings, and Workers observability to keep agent sessions reliable across requests.

Open dossier

Build applications, analyze traffic, and manage security settings through Cloudflare

Open dossier
Trust
Install riskReview firstReview firstReview firstLow risk
Notes Safety · Privacy · Safety Privacy Safety Privacy Safety Privacy
BrandCloudflare logoCloudflareCloudflare logoCloudflareCloudflare logoCloudflareCloudflare logoCloudflare
Categorytoolscollectionsguidesmcp
Sourcesource-backedsource-backedsource-backedfirst-party
AuthorCloudflareMkDev11MkDev11Cloudflare
Added2026-04-272026-06-042026-06-042025-09-18
Platforms
CLI
Claude Code
Claude Code
Claude CodeClaude Desktop
Source repo
Safety notes— missingThis collection runs nothing itself; linked entries can deploy Workers, inspect Cloudflare resources, or change app configuration. Use preview/staging environments and scoped API tokens before allowing Claude-assisted deployment or MCP operations. Review storage consistency, cache behavior, and rollback plans before moving AI workflows to production traffic.Keep model output reviewable before it triggers irreversible product actions, external messages, or billing-sensitive work. Store only the durable state the agent needs; avoid persisting full prompts, files, or transcripts when summaries or structured state are enough. Add idempotency and replay handling for events that may retry, arrive out of order, or resume after an agent instance restarts.Use a least-privilege Cloudflare token because DNS, security, Worker, and deployment actions can affect production services.
Privacy notes— missingThe collection stores no data itself; linked Cloudflare resources may process prompts, user requests, logs, analytics, object storage, or database rows. Workers AI and external model calls may involve account-level telemetry and provider-specific retention rules. Do not paste production secrets, customer data, or Cloudflare API tokens into transcripts or PR comments.Workers logs, Durable Object storage, Workers AI prompts, model outputs, request headers, and bound service data may contain user or business context. Redact sensitive fields before logging and define retention for prompts, intermediate reasoning, tool results, and conversation state. Separate staging and production state so test prompts and generated outputs cannot leak into live sessions.Zone settings, analytics, logs, account identifiers, deployment metadata, and security configuration may be sent through model context.
Prerequisites— none listed
  • A Cloudflare account, Wrangler authentication, and a target account/project for development or staging.
  • Agreement on which resources use Workers AI, Agents, D1, KV, R2, Queues, or external APIs.
  • Separate secrets and environment bindings for local, preview, staging, and production deployments.
  • A Cloudflare account with Workers, Workers AI, and Durable Objects available for the target environment.
  • Wrangler and a Worker project configured for TypeScript or JavaScript.
  • A clear state boundary, such as one agent per user, workspace, conversation, job, or document.
  • Test prompts, expected model responses, and sample state transitions for local or staging validation.
  • Cloudflare account with active zones
  • Cloudflare API Token from https://dash.cloudflare.com/profile/api-tokens
  • Cloudflare Account ID (found in Cloudflare dashboard)
  • Node.js and npm/npx available for running the @cloudflare/mcp-server-cloudflare package
Install
claude mcp add cloudflare --env CLOUDFLARE_API_TOKEN=YOUR_TOKEN --env CLOUDFLARE_ACCOUNT_ID=YOUR_ACCOUNT_ID && claude mcp list
Config
{
  "mcpServers": {
    "cloudflare": {
      "env": {
        "CLOUDFLARE_API_TOKEN": "${CLOUDFLARE_API_TOKEN}",
        "CLOUDFLARE_ACCOUNT_ID": "${CLOUDFLARE_ACCOUNT_ID}"
      },
      "args": [
        "-y",
        "@cloudflare/mcp-server-cloudflare"
      ],
      "command": "npx",
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.