Cloudflare Agents SDK
Cloudflare framework for building, deploying, and running AI agents on Workers with durable platform primitives.
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.
- Canonical URL
- https://heyclau.de/entry/tools/cloudflare-agents-sdk
- 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
- Scope
- Source repo
- 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
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 risk | Review first | Review first | Review first | Low risk |
| Notes | Safety · Privacy · | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | tools | collections | guides | mcp |
| Source | source-backed | source-backed | source-backed | first-party |
| Author | Cloudflare | MkDev11 | MkDev11 | Cloudflare |
| Added | 2026-04-27 | 2026-06-04 | 2026-06-04 | 2025-09-18 |
| Platforms | CLI | Claude Code | Claude Code | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | — missing | ✓This 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 | — missing | ✓The 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 |
|
|
|
| Install | — | — | — | |
| Config | — | — | — | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.