Add delivery and edge context to operational investigations.
Connect Cloudflare to d5s for authorized service, traffic, and delivery context used in incident triage and SEO diagnostics.
What agents can do with Cloudflare Developer Platform
Cloudflare evidence can help distinguish an application problem from an edge, traffic, or delivery issue. d5s agents use the connectable method inside an isolated investigation, preserve the observed window, and carry the evidence into the brief without being granted broad configuration authority.
- Inspect authorized delivery and service context
- Compare edge signals with application incidents
- Support crawl and availability diagnostics
Available connection methods
One public brand can have more than one verified access method. Pick the method that matches the workflow and credential policy.
MCP connection
MCP · oauth2
Manage Cloudflare accounts and KV storage namespaces, and list Workers.
Example compositions using Cloudflare Developer Platform
These examples show how the connector can participate in recurring work; they are patterns to build in d5s, not preinstalled workflow objects.
Morning operations brief
Review overnight incidents, group recurring signals, check the approved runbook, and deliver a source-linked morning handover.
See the workflow
Incident triage
Trace a production error, identify the likely change, and prepare a triage issue without giving the agent authority to modify production.
See the workflow
SEO monitoring brief
Review search performance, technical delivery, and competitor movement, then prepare a prioritized brief grounded in observable evidence.
See the workflowDeploy health check
After a release, compare error and delivery signals against the pre-release baseline and report whether anything moved beyond normal variance.
See the workflowTry asking
Connect Cloudflare Developer Platform to a governed workflow.
Each one arrives with a persona, standing instructions, a wake-up schedule, and its connectors chosen. Nothing runs until you add it.