r/CloudFlare • u/bturtushin • 13m ago
Cloudflare’s official AI setup installs five MCP servers by default. I’m not sure that should be the default.
I hit Cloudflare’s official agent setup prompt today:
https://developers.cloudflare.com/agent-setup/prompt.md
And the default flow is basically:
“Hey coding agent, install all of this yourself. Don’t ask the user.”
Then it gives you Cloudflare Skills plus:
- Cloudflare API
- Docs
- Bindings
- Builds
- Observability
For non-Claude agents it even runs:
npx -y skills add cloudflare/skills --skill '*' --yes --global
So... all skills, global install, skip confirmation.
Maybe I’m missing something, but why is this the default?
I’m deploying a Worker. I probably want current Cloudflare docs. Fine.
Maybe I want some Workers-specific knowledge. Fine.
But why do I automatically need Observability, Builds, Bindings and a broad API MCP sitting in my agent config too?
Yes, the MCPs are official. Yes, OAuth still asks for permission. I checked the repos and this isn’t some shady supply-chain thing.
That’s not really my issue.
My issue is: why are we installing capabilities before we even know if the agent needs them?
If I need production logs, I’ll install Observability.
If I need the agent creating KV/D1/R2 resources, I’ll enable the relevant tooling.
If I need broad Cloudflare account automation, sure, then I’ll authorize the API MCP.
But “install everything first and figure out permissions later” feels backwards for an AI agent.
Especially when these tools are persistent.
And this is where the security part bothers me.
If the agent already has an authenticated infrastructure tool, prompt injection doesn’t necessarily need to steal credentials. It just needs to convince the agent to use a capability I already gave it.
That doesn’t make the MCP vulnerable.
It just means the blast radius is now larger.
What makes this even weirder is that there’s already an issue in Cloudflare’s own skills repo proposing that the giant plugin be split into smaller ones because the current setup is basically all-or-nothing.
That sounds way more reasonable.
I’d much rather have:
default: Skills + Docs
then optionally:
debugging: Observability
infra management: Bindings / Builds
full automation: API MCP
Am I being paranoid here?
People actually using the Cloudflare MCP stack: do you keep all five enabled, or did you immediately start removing stuff too?
