What an agent can do in Cloudflare (Workers Bindings)
Build and manage Cloudflare Workers apps: work with bindings like KV, R2, D1 and Durable Objects, and deploy/configure Workers.
Jobs on Rush that use Cloudflare (Workers Bindings)
- Inventory Cloudflare Workers and Their Bindings
- Fix Cloudflare Worker Errors From Its Logs
- Fix Errors in a Hono Deployment
How Cloudflare (Workers Bindings) connects
Cloudflare (Workers Bindings) is a remote MCP server, published by Cloudflare, at https://bindings.mcp.cloudflare.com/mcp. Connecting it signs in through the MCP OAuth flow on Cloudflare (Workers Bindings)'s side.
From Cloudflare: Cloudflare (Workers Bindings)'s MCP documentation · source code.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names cloudflare in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "Cloudflare",
"url": "https://bindings.mcp.cloudflare.com/mcp"
}Whose Cloudflare (Workers Bindings) account the agent uses
Your Cloudflare (Workers Bindings) connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Cloudflare (Workers Bindings), and a run started with an API key uses the Cloudflare (Workers Bindings) of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Cloudflare (Workers Bindings), and that agent's runs use their account and nothing else: never yours, never another user's.
More Cloud integrations
Frequently asked questions
How do I connect Cloudflare (Workers Bindings) to Rush?
Open Settings → Connections in the console and connect Cloudflare (Workers Bindings), or send POST /me/connections with {"type":"mcp","name":"Cloudflare","url":"https://bindings.mcp.cloudflare.com/mcp"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my Cloudflare (Workers Bindings) account?
No. A run gets your Cloudflare (Workers Bindings) connection only when it names it in connections ("connections": ["cloudflare"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in Cloudflare (Workers Bindings)?
Build and manage Cloudflare Workers apps: work with bindings like KV, R2, D1 and Durable Objects, and deploy/configure Workers. 3 published jobs use it; this page lists them.
Can my app's users connect their own Cloudflare (Workers Bindings)?
Yes. Make each user an agent from your template, and they sign in to their own Cloudflare (Workers Bindings) through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.
Keep reading
- AI agents for engineering teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to