Cloudflare MCP MCP integration for AI agents.
Connect AI agents to Cloudflare MCP through 3 structured actions, including search, execute, and docs. Review authentication, inputs, workflows, and safety g…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- OAuth 2.0 + API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Cloudflare MCP integration exposes
The Cloudflare MCP Agent App exposes 3 provider-backed actions for developer tools and infrastructure work. Its current contract lets an authorized agent run sandboxed javascript against cloudflare's openapi specification to discover api endpoints and parameters, run sandboxed javascript on cloudflare's official mcp server to call cloudflare api endpoints discovered with `search`, and search the official cloudflare developer documentation for relevant guidance and examples. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Cloudflare MCP account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Cloudflare MCP capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
searchREADRun sandboxed JavaScript against Cloudflare's OpenAPI specification to discover API endpoints and parameters.
INPUTS: code
executeWRITERun sandboxed JavaScript on Cloudflare's official MCP server to call Cloudflare API endpoints discovered with `search`.
INPUTS: code / account_id
docsREVIEWSearch the official Cloudflare developer documentation for relevant guidance and examples.
INPUTS: query
INPUT CONTRACTS
Know what the action needs before it runs.
search
codeREQUIRED- A JavaScript async arrow function. Use `search` before `execute` to discover the exact Cloudflare API path and parameters.
execute
codeREQUIRED- A JavaScript async arrow function. Use `search` before `execute` to discover the exact Cloudflare API path and parameters.
account_idOPTIONAL- An optional Cloudflare account ID. Supply it for a user token when the operation is account-scoped; account tokens are auto-detected.
docs
queryREQUIRED- The Cloudflare documentation search query.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Search
Run sandboxed JavaScript against Cloudflare's OpenAPI specification to discover API endpoints and parameters. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
searchControl Execute
Run sandboxed JavaScript on Cloudflare's official MCP server to call Cloudflare API endpoints discovered with `search`. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
executeVerify with Execute
Run sandboxed JavaScript on Cloudflare's official MCP server to call Cloudflare API endpoints discovered with `search`. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
executeSAFETY BOUNDARY
Operate Cloudflare MCP with explicit limits
- Authorize Cloudflare MCP with OAuth 2.0 and API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Cloudflare MCP rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Cloudflare MCP task completed successfully.
CONNECTION MODEL
OAuth 2.0 + API key
A Cloudflare user or account API token sent to the official MCP server as an Authorization Bearer token. Grant only the permissions needed by your workflows. Account tokens should also include Account Resources: Read so the MCP server can auto-detect the account ID.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Cloudflare MCP.