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.
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.
Privacy notes
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.
Author
MkDev11
Submitted by
MkDev11
Claim status
unclaimed
Last verified
2026-06-04
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
78
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Complete
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
Registry metadata indicates a reviewed listing.
Done
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
3 safety and 3 privacy notes across 5 risk areas. Review closely: credentials & tokens, network access, third-party handling.
5 areas
SafetyExecution & processesThis collection runs nothing itself; linked entries can deploy Workers, inspect Cloudflare resources, or change app configuration.
SafetyCredentials & tokensUse preview/staging environments and scoped API tokens before allowing Claude-assisted deployment or MCP operations.
SafetyData retentionReview storage consistency, cache behavior, and rollback plans before moving AI workflows to production traffic.
PrivacyNetwork accessThe collection stores no data itself; linked Cloudflare resources may process prompts, user requests, logs, analytics, object storage, or database rows.
PrivacyThird-party handlingWorkers AI and external model calls may involve account-level telemetry and provider-specific retention rules.
PrivacyCredentials & tokensDo not paste production secrets, customer data, or Cloudflare API tokens into transcripts or PR comments.
Safety notes
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.
Privacy notes
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.
Prerequisites
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.
## What this collection sets up
This bundle is for builders shipping AI applications on Cloudflare's edge
platform. It pairs app architecture guidance with deployment operations, storage
boundaries, MCP access, and operational checks so Claude can help without
blurring the line between preview and production resources.
## Layers
### 1. AI runtime and application shape
- **cloudflare-agents-sdk** provides the Cloudflare Agents foundation for
agentic apps on Workers.
- **cloudflare-workers-ai-edge** focuses on Workers AI usage, bindings, and
edge inference patterns.
### 2. Durable state and platform boundaries
- **cloudflare-workers-d1-kv-r2-capability-pack** covers storage tradeoffs for
D1, KV, and R2.
- **environment-variable-validator** helps keep account IDs, tokens, and
environment bindings explicit before running deployment workflows.
### 3. Deploy, operate, and iterate
- **wrangler-deployment-operations-capability-pack** handles Wrangler planning,
deploys, versions, and rollback thinking.
- **cloudflare-mcp-server** exposes Cloudflare operations through MCP when
scoped credentials are approved.
- **github-actions-ai-cicd** and **performance-impact-monitor** keep CI and
performance feedback in the loop.
- **zero-budget-saas-launch-capability-pack** helps constrain launch scope and
free-tier assumptions for early SaaS experiments.
## Suggested order
Start by defining the Workers/Agents runtime and storage boundaries, then set up
Wrangler and environment validation, then connect Cloudflare MCP and CI/CD.
Keep production tokens out of early experiments and make rollback paths part of
the first deployment plan.
## Source and references
- Cloudflare Workers documentation: https://developers.cloudflare.com/workers/
- Workers AI documentation: https://developers.cloudflare.com/workers-ai/
- Cloudflare Agents documentation: https://developers.cloudflare.com/agents/
- Wrangler documentation: https://developers.cloudflare.com/workers/wrangler/
## Duplicate check
Checked existing collections, upstream collection history, open collection PRs,
and repository content for `cloudflare-ai-app-builder`, Cloudflare AI app,
Workers AI collection, Cloudflare Agents workflow, and Wrangler deployment
collection. Existing AWS, backend, API, data, and SaaS MCP collections do not
provide a Cloudflare-specific AI app builder bundle around Workers, Agents,
Workers AI, storage primitives, Wrangler, and Cloudflare MCP.
## Disclosure
Editorial collection. No paid placement or affiliate link is used.
About this resource
What this collection sets up
This bundle is for builders shipping AI applications on Cloudflare's edge
platform. It pairs app architecture guidance with deployment operations, storage
boundaries, MCP access, and operational checks so Claude can help without
blurring the line between preview and production resources.
Layers
1. AI runtime and application shape
cloudflare-agents-sdk provides the Cloudflare Agents foundation for
agentic apps on Workers.
cloudflare-workers-ai-edge focuses on Workers AI usage, bindings, and
edge inference patterns.
2. Durable state and platform boundaries
cloudflare-workers-d1-kv-r2-capability-pack covers storage tradeoffs for
D1, KV, and R2.
environment-variable-validator helps keep account IDs, tokens, and
environment bindings explicit before running deployment workflows.
3. Deploy, operate, and iterate
wrangler-deployment-operations-capability-pack handles Wrangler planning,
deploys, versions, and rollback thinking.
cloudflare-mcp-server exposes Cloudflare operations through MCP when
scoped credentials are approved.
github-actions-ai-cicd and performance-impact-monitor keep CI and
performance feedback in the loop.
zero-budget-saas-launch-capability-pack helps constrain launch scope and
free-tier assumptions for early SaaS experiments.
Suggested order
Start by defining the Workers/Agents runtime and storage boundaries, then set up
Wrangler and environment validation, then connect Cloudflare MCP and CI/CD.
Keep production tokens out of early experiments and make rollback paths part of
the first deployment plan.
Checked existing collections, upstream collection history, open collection PRs,
and repository content for cloudflare-ai-app-builder, Cloudflare AI app,
Workers AI collection, Cloudflare Agents workflow, and Wrangler deployment
collection. Existing AWS, backend, API, data, and SaaS MCP collections do not
provide a Cloudflare-specific AI app builder bundle around Workers, Agents,
Workers AI, storage primitives, Wrangler, and Cloudflare MCP.
Disclosure
Editorial collection. No paid placement or affiliate link is used.
Show that Cloudflare AI App Builder is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/collections/cloudflare-ai-app-builder)
How it compares
Cloudflare AI App Builder side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
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.
Run AI inference and serverless functions on Cloudflare Workers AI: call hosted models like Llama, Whisper, and Stable Diffusion through the Workers AI binding, deploy with wrangler, and use D1/R2/KV storage plus the free daily Neuron allocation.
✓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.
✓May produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first.
Use least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.
✓Use this skill as planning or review guidance; verify generated commands, code, configuration, and infrastructure changes before running them.
Apply least-privilege credentials and test in staging or a disposable branch before using it on production systems, CI, deployment, or account-write workflows.
✓Deploying with wrangler writes Workers and bindings to your Cloudflare account; review what you deploy, since it serves live traffic.
Running Workers AI models consumes paid Neurons beyond the free daily allocation; set usage expectations before deploying inference at scale.
Privacy notes
✓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.
✓Inputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration.
Redact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.
✓Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model.
Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.
✓Requests sent to Workers AI models are processed on Cloudflare's network; review what data your function forwards to the model.
Keep Cloudflare API tokens in wrangler's secret store or environment variables, never hard-coded or committed.
Prerequisites
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.