
Cloudflare Workers Bindings
GAManage the D1, KV, R2, and Hyperdrive bindings a Cloudflare Worker depends on.
How it works
Every agent request passes through Ferentin policy before it reaches Cloudflare Workers Bindings.- AI agentAsks for something
- Ferentin policies
- OAuth 2.0 consent
- Per user authorization
- Dynamic client registration
- PKCE
- Cloudflare Workers Bindings MCP serverAuthorized connection
- Governed resultMasked, logged, returned
What you can do with Cloudflare Workers Bindings
Discover
Search and browse what exists, without opening the content itself.
7 tools
Access
Read content and metadata, subject to masking policy.
6 tools
Manage
Create, update, organise and remove items.
9 tools
Technical capabilities23 tools
Discover
- kv_namespaces_list
- workers_list
- r2_buckets_list
- d1_databases_list
- d1_database_query
- hyperdrive_configs_list
- search_cloudflare_documentation
Access
- kv_namespace_get
- workers_get_worker
- workers_get_worker_code
- r2_bucket_get
- d1_database_get
- hyperdrive_config_get
Manage
- kv_namespace_create
- kv_namespace_delete
- kv_namespace_update
- r2_bucket_create
- r2_bucket_delete
- d1_database_create
- d1_database_delete
- hyperdrive_config_delete
- hyperdrive_config_edit
Other
- migrate_pages_to_workers_guide
Overview
Cloudflare Workers bind to platform primitives — D1 SQL databases, KV namespaces, R2 buckets, and Hyperdrive connection configs — which together make up the storage and data layer of a Workers application.
Ferentin integration
With OAuth2 authorization granted, an AI agent can list, create, inspect, and delete those bindings, query D1 directly, and read a Worker's source — enough to stand up and evolve a Workers backend from natural language.
Frequently asked about Cloudflare Workers Bindings
- What can AI agents do with Cloudflare Workers Bindings through Ferentin?
- Ferentin exposes 23 Cloudflare Workers Bindings MCP tools to your AI agents, grouped as Discover (7 tools), Access (6 tools) and Manage (9 tools). Every call is checked against your Ferentin policies before it reaches Cloudflare Workers Bindings.
- How does Ferentin secure Cloudflare Workers Bindings access?
- Requests through the Cloudflare Workers Bindings integration are covered by OAuth 2.0 consent, per user authorization, dynamic client registration, PKCE and audit logging. These controls are applied by Ferentin, not by Cloudflare Workers Bindings, so they hold across every connected agent.
- How do I connect Cloudflare Workers Bindings to Ferentin?
- Open the Ferentin admin console, add Cloudflare Workers Bindings as a new connection and authenticate with OAuth 2.0. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.
- Is the Cloudflare Workers Bindings integration generally available?
- Yes. The Cloudflare Workers Bindings integration is generally available on Ferentin, including the free tier.
Related integrations
3
Cloudflare
Manage Cloudflare — DNS, Workers, Zero Trust, observability, and more — across 2,500+ API endpoints via a search-and-execute agent surface.

Cloudflare Workers Builds
Diagnose Cloudflare Workers deployments — build history, status, and logs.

Supabase
Open source Firebase alternative with Postgres database, auth, edge functions, and real-time subscriptions.