Skip to main content
collectionsSource-backed
Cloudflare logo

Cloudflare AI App Builder

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.

by MkDev11·added 2026-06-04·
Bundle:9 items
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/workers/, https://github.com/JSONbored/awesome-claude/blob/main/content/collections/cloudflare-ai-app-builder.mdx
Brand
Cloudflare
Brand domain
cloudflare.com
Brand asset source
brandfetch
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.
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.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

80 minutes

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.

0/3 ready
Account & credentials1Review & approval1General180 minutes

Safety & privacy surface

Safety & privacy surface

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.

Schema details

Install type
copy
Troubleshooting
No
Collection metadata
Items
9 entries
Estimated setup
80 minutes
Difficulty
advanced
Installation order
cloudflare-agents-sdkcloudflare-workers-ai-edgecloudflare-workers-d1-kv-r2-capability-packwrangler-deployment-operations-capability-packcloudflare-mcp-serverenvironment-variable-validatorgithub-actions-ai-cicdperformance-impact-monitorzero-budget-saas-launch-capability-pack
Full copyable content
## 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.

Source and references

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.

Source citations

Add this badge to your README

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.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/collections/cloudflare-ai-app-builder.svg)](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.

Field

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

Expert Cloudflare capability skill for designing workers that combine D1, KV, and R2 with clear consistency, caching, and security boundaries.

Open dossier

Expert zero-budget launch capability pack for building and shipping SaaS using free-tier infrastructure and constrained execution plans.

Open dossier

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.

Open dossier
Next stepsDiffers
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage not verifiedPackage verified2026-04-10Package verified2026-04-11Package verified2025-10-16
Source provenanceDiffersSource-backedNo submission linkNo submission linkNo submission link
SubmitterDiffersMkDev11
Install riskReview firstLow riskLow riskLow risk
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandCloudflare logoCloudflareCloudflare logoCloudflareCloudflare logoCloudflare
Categorycollectionsskillsskillsskills
SourceSource-backedFirst-partyFirst-partyFirst-party
AuthorMkDev11JSONboredJSONboredJSONbored
Added2026-06-042026-04-102026-04-112025-10-16
Platforms
Harness
Source repo
Safety notesThis 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 notesThe 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.
  • Cloudflare account and worker project
  • D1/KV/R2 bindings access
  • Defined data model and SLA targets
  • Product hypothesis
  • Free-tier account access
  • Launch KPI targets
  • Cloudflare account
  • Wrangler CLI 3.0+
  • Node.js 18+
  • @cloudflare/workers-types
Install
curl -L https://heyclau.de/downloads/skills/cloudflare-workers-d1-kv-r2-capability-pack.zip -o cloudflare-workers-d1-kv-r2-capability-pack.zip && unzip -o cloudflare-workers-d1-kv-r2-capability-pack.zip -d ./cloudflare-workers-d1-kv-r2-capability-pack
curl -L https://heyclau.de/downloads/skills/zero-budget-saas-launch-capability-pack.zip -o zero-budget-saas-launch-capability-pack.zip && unzip -o zero-budget-saas-launch-capability-pack.zip -d ./zero-budget-saas-launch-capability-pack
npm install -g wrangler
Config
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

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