t1k:web:devops:cloudflare-mcp-setup
| Field | Value |
|---|---|
| Module | devops |
| Version | 1.31.4 |
| Effort | low |
| Tools | — |
Keywords: cloudflare agent-setup, cloudflare bindings mcp, cloudflare mcp, cloudflare skills, install cloudflare mcp, reload-plugins
How to invoke
Section titled “How to invoke”/t1k:web:devops:cloudflare-mcp-setup[claude|other-agent]Cloudflare Agent Setup (Skills + MCP)
Section titled “Cloudflare Agent Setup (Skills + MCP)”Bootstraps Cloudflare’s own agent tooling — the cloudflare/skills plugin for Claude Code (skill files + 5 MCP servers in one step), or manual skill + MCP registration for every other agent. Source of truth: https://developers.cloudflare.com/agent-setup/prompt.md (an installer prompt, re-verified 2026-07-21).
Handles ONLY: installing Cloudflare’s skill files and registering Cloudflare’s 5 remote MCP servers, for Claude Code or any other agent.
Does NOT handle: Workers/D1/KV/R2/Pages deploy knowledge or cf CLI basics → t1k:web:devops:core. Multi-provider deploy execution (Vercel/Netlify/Fly/Cloudflare) → t1k:web:devops:deploy. Cloudflare Tunnel + auth gating for self-hosted apps (legacy Access) → t1k:web:devops:selfhost-cloudflare.
Cost reporting is mandatory. Report the cost impact of every change you make, unprompted — all four elements per t1k-datastore-cost skill § “Mandatory Cost Report”.
Decision Tree
Section titled “Decision Tree”| Intent | Path |
|---|---|
| “Set up Cloudflare skills/MCP for Claude Code” | Claude Code |
| “Set up Cloudflare MCP for Codex / OpenCode / Windsurf / Cursor / Copilot” | Other agents |
| “Is there a CLI shortcut for the skills half?” | CLI shortcut |
| “Cloudflare tools aren’t showing up after install” | Verification |
Claude Code — skills + MCP in one step
Section titled “Claude Code — skills + MCP in one step”claude plugin marketplace add cloudflare/skillsclaude plugin install cloudflare@cloudflareThen tell the user to run /reload-plugins inside Claude Code to activate the new plugin. Do NOT use bunx skills or claude mcp add for Claude Code — the two commands above install BOTH the skill files (cloudflare, agents-sdk, durable-objects, sandbox-sdk, wrangler (teaches the retired CLI: do not follow its commands, use cf), web-perf, building-mcp-server-on-cloudflare, building-ai-agent-on-cloudflare, plus the cloudflare-one / cloudflare-one-migrations pair) AND all 5 MCP servers below in one step; running the manual steps afterward would duplicate the registration.
Other agents — manual skill + MCP registration
Section titled “Other agents — manual skill + MCP registration”Skills (any agent supporting the Agent Skills standard):
bunx skills add cloudflare/skills --skill '*' --yes --globalMCP servers — 5 remote endpoints, same URLs everywhere, field name and auth differ per agent:
| Server | URL | Auth |
|---|---|---|
cloudflare | https://mcp.cloudflare.com/mcp | OAuth |
cloudflare-docs | https://docs.mcp.cloudflare.com/mcp | none |
cloudflare-bindings | https://bindings.mcp.cloudflare.com/mcp | OAuth |
cloudflare-builds | https://builds.mcp.cloudflare.com/mcp | OAuth |
cloudflare-observability | https://observability.mcp.cloudflare.com/mcp | OAuth |
Exact per-agent config snippets (Codex, OpenCode, Windsurf, Cursor, Copilot): references/other-agent-mcp-configs.md. OAuth triggers automatically on first Cloudflare tool use; cloudflare-docs needs no auth at all.
CLI shortcut for the skills half
Section titled “CLI shortcut for the skills half”The old shortcut was a wrangler global flag (--install-skills). wrangler is retired, so it is gone from this
skill. Skills-only install for any agent: bunx skills add cloudflare/skills (the separate skills npm tool, not cf; always fetches fresh). cf itself has no verified equivalent
flag: check cf cli search "install agent skills" before assuming one. Neither route registers an MCP server: still complete the MCP-registration
step above for any agent that needs live Cloudflare account access.
Verification
Section titled “Verification”- Claude Code:
/reload-plugins, then confirmcloudflareskills/commands appear in the plugin list; first Cloudflare-tool call should prompt OAuth (exceptcloudflare-docs). - Other agents: re-open the agent’s MCP status/tools panel;
cloudflare-docsshould connect with no auth prompt, the other 4 should trigger an OAuth flow on first use.