Provider · Deploy

Cloudflare — Ashlr Stack Provider

Cloudflare: Workers, R2, D1. Account id inferred from the token's scope. Review adapter-specific setup, credential and MCP requirements in Ashlr Stack.

Deploy · PAT

Cloudflare — Workers, R2, D1. Account id inferred from the token's scope.

Dashboard ↗

One command

Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results.

stack add cloudflare

Or retrieve catalog matches for what you're building via stack recommend:

stack recommend "host a Next.js frontend"

Auth flow

Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource.

How-to: Create a scoped API token at https://dash.cloudflare.com/profile/api-tokens.

Secret slots

stack add cloudflare has these 2 catalog secret slots; verify which values its adapter actually materializes through Phantom:

CLOUDFLARE_API_TOKEN
CLOUDFLARE_ACCOUNT_ID

Use stack env export --example for an empty-key skeleton. Stack does not automatically fill env files or resolve credential placeholders. stack exec -- <cmd> forwards to installed Phantom exec; configure and verify the app separately.

MCP wiring

Cloudflare has an MCP entry in the catalog. An adapter may write a descriptor to .mcp.json. Inspect the actual file and complete supported client and credential setup; Claude Code / Cursor / Windsurf availability is not established by the descriptor. Shell expressions in JSON remain literal.

Cloudflare MCP (Workers Bindings + R2 + D1) with CLOUDFLARE_API_TOKEN piped from Phantom.

Starter templates that include Cloudflare

Selected template init attempts provider setup by default; add --noProvision to inspect config first:

stack init --template cloudflare-turso-clerk

Modal — Serverless compute for AI + data. Token stored in Phantom.
Vercel — Frontend platform. Stores a scoped access token for deploys + env sync.
Railway — Infra from a repo. Project-level token stored in Phantom.
Fly.io — VMs at the edge. Machines API token stored in Phantom.
Render — Zero-config hosting. API key stored in Phantom.

FAQ

Do I need a Cloudflare account to use it with Stack?

Use an existing Cloudflare account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource. If you don't have a credential yet, create one at https://dash.cloudflare.com and supply the required inputs; inspect verification and persistence results.

Where does Stack store my Cloudflare credentials?

Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.

Can I rotate or revoke this integration later?

Use `stack remove cloudflare` for local Cloudflare configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Cloudflare credentials through https://dash.cloudflare.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.