Cloudflare Docs MCP integration for AI agents.
Connect AI agents to Cloudflare Docs through 2 structured actions, including get pages to workers migration guide and search cloudflare documentation. Review…
- ACTION CONTRACTS
- 2
- AUTHENTICATION
- Custom credentials
- 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 Docs integration exposes
The Cloudflare Docs Agent App exposes 2 provider-backed actions for developer tools and ai work. Its current contract lets an authorized agent get the guide and instructions for migrating cloudflare pages projects to cloudflare workers and search cloudflare documentation for workers, pages, r2, images, stream, d1, durable objects, kv, workflows, hyperdrive, queues, ai search, workers ai, vectorize, ai gateway, browser run, zero trust, access, tunnel, gateway, browser isolation, warp, ddos, magic transit, magic wan, cdn, cache, dns, zaraz, argo, rulesets, terraform, account and billing. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. 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 Docs account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Cloudflare Docs capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_pages_to_workers_migration_guideREADGet the guide and instructions for migrating Cloudflare Pages projects to Cloudflare Workers.
search_cloudflare_documentationREADSearch Cloudflare documentation for Workers, Pages, R2, Images, Stream, D1, Durable Objects, KV, Workflows, Hyperdrive, Queues, AI Search, Workers AI, Vectorize, AI Gateway, Browser Run, Zero Trust, Access, Tunnel, Gateway, Browser Isolation, WARP, DDOS, Magic Transit, Magic WAN, CDN, Cache, DNS, Zaraz, Argo, Rulesets, Terraform, Account and Billing.
INPUTS: query
INPUT CONTRACTS
Know what the action needs before it runs.
search_cloudflare_documentation
queryOPTIONAL- Search query for Cloudflare documentation.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Pages To Workers Migration Guide
Get the guide and instructions for migrating Cloudflare Pages projects to Cloudflare Workers. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_pages_to_workers_migration_guideVerify with Search Cloudflare Documentation
Search Cloudflare documentation for Workers, Pages, R2, Images, Stream, D1, Durable Objects, KV, Workflows, Hyperdrive, Queues, AI Search, Workers AI, Vectorize, AI Gateway, Browser Run, Zero Trust, Access, Tunnel, Gateway, Browser Isolation, WARP, DDOS, Magic Transit, Magic WAN, CDN, Cache, DNS, Zaraz, Argo, Rulesets, Terraform, Account and Billing. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
search_cloudflare_documentationSAFETY BOUNDARY
Operate Cloudflare Docs with explicit limits
- Authorize Cloudflare Docs with Custom credentials and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Cloudflare Docs data may still be sensitive and should be minimized before it enters model context.
- 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 Docs rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Cloudflare Docs task completed successfully.
CONNECTION MODEL
Custom credentials
Cloudflare Docs uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
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
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 Docs.