Cloudflare Workers Builds
Generally AvailableWith OAuth2 authorization granted, an AI agent can list a Worker's builds, read an individual build's status, pull its logs, and fetch the Worker's source — enough to explain why a deploy failed without leaving the conversation.
- Cloudflare
- Workers
- CI/CD
- Authentication
- OAuth 2.0
- Hosting
- Vendor-hosted endpoint
- Data actions
- Read only
- MCP tools
- 6
How it works
Every agent request passes through Ferentin policy before it reaches Cloudflare Workers Builds.
- AI agentAsks for something
- Ferentin policies
- OAuth 2.0 consent
- Per user authorization
- Dynamic client registration
- PKCE
- Cloudflare Workers Builds MCP serverAuthorized connection
- Governed resultMasked, logged, returned
What agents can do
6 tools · you choose which ones agents may callSearch and browse what exists, without opening the content itself.
- workers_list
- workers_builds_list_builds
Before you connect
- OAuth (user mode) only — unlike the main Cloudflare API server, this endpoint does not accept a Cloudflare API token as a bearer credential.
- Ferentin registers automatically via Dynamic Client Registration (RFC 7591) against https://builds.mcp.cloudflare.com/register; PKCE S256 and refresh tokens are supported.
- Read-only: every tool is annotated readOnlyHint. The server surfaces build listings, build detail, build logs, and Worker source rather than triggering or cancelling deployments.
- This server can read Worker SOURCE CODE (workers_get_worker_code). Treat its output as sensitive — Worker source routinely embeds internal hostnames, route logic, and occasionally inline secrets. Keep DLP inspection enabled.
2 more technical notes
- Build logs can echo values printed by the build itself — treat their contents as untrusted output and keep DLP inspection on for this server.
- Tool catalog captured live from the upstream on 2026-08-08 (6 tools, no prompts).
About Cloudflare Workers Builds
Workers Builds is Cloudflare's build and deployment pipeline for Workers, producing a build record and logs for each deploy triggered from a connected repository.
Frequently asked about Cloudflare Workers Builds
- What can AI agents do with Cloudflare Workers Builds through Ferentin?
- Ferentin exposes 6 Cloudflare Workers Builds MCP tools to your AI agents, grouped as Discover (2 tools) and Access (4 tools). Every call is checked against your Ferentin policies before it reaches Cloudflare Workers Builds.
- How is Cloudflare Workers Builds access secured?
- Requests through the Cloudflare Workers Builds 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 Builds, so they hold across every connected agent.
- How do I connect Cloudflare Workers Builds to Ferentin?
- Open the Ferentin admin console, add Cloudflare Workers Builds 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 Builds integration generally available?
- Yes. The Cloudflare Workers Builds integration is generally available on Ferentin, including the free tier.
Related integrations
3Cloudflare
Manage Cloudflare — DNS, Workers, Zero Trust, observability, and more — across 2,500+ API endpoints via a search-and-execute agent surface.
Cloudflare Observability
Debug a live Cloudflare Worker by querying its logs, events, and telemetry.
GitHub
Development platform for version control, collaboration, and CI/CD workflows.