Give your app storage, email, and an edge deploy in the Cloudflare account you control.
Describe the result in chat. The agent installs the integration, wires the app, and checks the connection before you ship.
What the agent sets up
One request covers the app code, provider connection, and working proof.
Connects the project to Cloudflare and provisions the resources the app actually needs.
Wires storage and email from server-owned code instead of leaking the account token into the app.
Checks account access, Workers billing, and domain verification with a specific remedy for each blocker.
Values stay out of the conversation
Private values stay server-side. Stored values are resolved only by server tools. The agent receives the field name, runtime, verification status, and fix-it link, never the stored value.
Scoped Cloudflare API token used by Contrast to provision project R2 and probe Email Sending.
Create or manage this keyA blocker comes with the next move
Contrast probes https://api.cloudflare.com/client/v4 from the server. It classifies a missing key, invalid key or permission, and an unreachable provider separately instead of returning a generic failure.
Each blocked result explains what failed and links to the provider screen where you can fix it. Run verification again and the project moves to Verified only after the provider accepts the probe.
Ship the stack you used while building
The same project moves from preview to Cloudflare with its database, storage, email, and server code intact. You keep control of the account and the provisioned resources.