Cloudflare + Conductor
Conductor connects to one or more Cloudflare accounts and lets an agent attach Cloudflare's own MCP — so the same agent that drives your fleet can also drive Cloudflare (DNS, zone settings, analytics).
1. Connect an account (multi-account)
- Create a Cloudflare API token (My Profile → API Tokens). For managing DNS + SSL, grant Zone → DNS → Edit and Zone → Zone Settings → Edit (and Zone → Zone → Read). Token can be account- or zone-scoped.
- In Conductor, Credentials → Add Credential, provider Cloudflare, paste the token as the API key, name it after the account (e.g.
intellecta,inventlist). - Click Verify — Conductor checks the token (by listing zones, so account-scoped tokens work too) and caches the account's zones, so it knows which account owns which domain.
Repeat for each account. Both connect side by side, and each domain resolves to whichever account owns its zone.
2. Attach Cloudflare's MCP
Cloudflare hosts remote MCP servers (you connect a client to them; Conductor doesn't self-host them). Auth is OAuth — it triggers automatically on first tool use, so there's no token in the attach command. The main one wraps the Cloudflare API behind search() / execute().
Servers (per Cloudflare's agent-setup):
| Name | URL |
|---|---|
cloudflare (main API) |
https://mcp.cloudflare.com/mcp |
cloudflare-docs (public, no auth) |
https://docs.mcp.cloudflare.com/mcp |
cloudflare-bindings |
https://bindings.mcp.cloudflare.com/mcp |
cloudflare-builds |
https://builds.mcp.cloudflare.com/mcp |
cloudflare-observability |
https://observability.mcp.cloudflare.com/mcp |
Claude Code — use the plugin (recommended):
claude plugin marketplace add cloudflare/skills
claude plugin install cloudflare@cloudflare
# then run /reload-plugins inside Claude
Other MCP clients — add the server (OAuth on first use), named per account:
claude mcp add --transport http cloudflare-<account> https://mcp.cloudflare.com/mcp
Once attached, your agent has Conductor's tools and Cloudflare's over the same fleet — inspect a zone, flip a record to proxied, read DNS analytics, inline.
Direct actions vs MCP
- Conductor's own buttons ("Put behind Cloudflare") call the Cloudflare API directly with the stored token — deterministic, no agent needed.
- Cloudflare's MCP is for agent-driven, ad-hoc work (debugging, analytics, one-off changes).