Cloudflare Email Routing MCP integration for AI agents.
Connect AI agents to Cloudflare Email Routing through 5 structured actions, including list destination addresses, create routing rule, and delete routing rul…
- ACTION CONTRACTS
- 5
- 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 Email Routing integration exposes
The Cloudflare Email Routing Agent App exposes 5 provider-backed actions for communication and developer tools work. Its current contract lets an authorized agent list cloudflare email routing destination addresses. use addresses with a non-null verified timestamp for forward actions, create a cloudflare email routing rule in a zone. forward actions require verified destination addresses, and delete a cloudflare email routing rule from a zone. 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 Email Routing account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Cloudflare Email Routing capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_destination_addressesREADList Cloudflare Email Routing destination addresses. Use addresses with a non-null verified timestamp for forward actions.
INPUTS: accountId / direction / verified / page / perPage
create_routing_ruleWRITECreate a Cloudflare Email Routing rule in a zone. Forward actions require verified destination addresses.
INPUTS: zoneId / actions / matchers / enabled / name
delete_routing_ruleHIGH IMPACTDelete a Cloudflare Email Routing rule from a zone.
INPUTS: zoneId / ruleId
list_routing_rulesREADList Cloudflare Email Routing rules for a zone or account.
INPUTS: zoneId / accountId / enabled / page / perPage
update_routing_ruleWRITEReplace a Cloudflare Email Routing rule in a zone.
INPUTS: zoneId / ruleId / actions / matchers / enabled
INPUT CONTRACTS
Know what the action needs before it runs.
list_destination_addresses
accountIdOPTIONAL- The Cloudflare account ID.
directionOPTIONAL- The result sort direction.
verifiedOPTIONAL- Filter by destination address verification status.
pageOPTIONAL- The result page number.
perPageOPTIONAL- The page size.
create_routing_rule
zoneIdOPTIONAL- The Cloudflare zone ID.
actionsREQUIRED- Actions applied to matching email.
matchersREQUIRED- Conditions matching incoming email.
enabledOPTIONAL- Whether the rule is enabled.
nameOPTIONAL- The rule name.
delete_routing_rule
zoneIdOPTIONAL- The Cloudflare zone ID.
ruleIdREQUIRED- The Cloudflare routing rule ID.
list_routing_rules
zoneIdOPTIONAL- The Cloudflare zone ID.
accountIdOPTIONAL- The Cloudflare account ID.
enabledOPTIONAL- Filter by enabled routing rules.
pageOPTIONAL- The result page number.
perPageOPTIONAL- The page size.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Destination Addresses
List Cloudflare Email Routing destination addresses. Use addresses with a non-null verified timestamp for forward actions. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_destination_addressesControl Create Routing Rule
Create a Cloudflare Email Routing rule in a zone. Forward actions require verified destination addresses. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_routing_ruleVerify with List Routing Rules
List Cloudflare Email Routing rules for a zone or account. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_routing_rulesSAFETY BOUNDARY
Operate Cloudflare Email Routing with explicit limits
- Authorize Cloudflare Email Routing with Custom credentials and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_routing_rule` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `Email Routing Rules Write`, `Email Routing Addresses Read`, and `Email Routing Rules Read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Cloudflare Email Routing task completed successfully.
CONNECTION MODEL
Custom credentials
Cloudflare Email Routing 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
- 2
- HIGH IMPACT
- 1
- 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 Email Routing.