t1k:web:devops:cloudflare-mcp-setup

Field	Value
Module	`devops`
Version	`1.11.0`
Effort	`low`
Tools	—

Keywords: cloudflare agent-setup, cloudflare bindings mcp, cloudflare mcp, cloudflare skills, install cloudflare mcp, reload-plugins

How to invoke

/t1k:web:devops:cloudflare-mcp-setup
[claude|other-agent]

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).

Scope

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 wrangler basics → t1k:web:devops:core. Multi-provider deploy execution (Vercel/Netlify/Fly/Cloudflare) → t1k:web:devops:deploy. Cloudflare Tunnel + Zero Trust Access for self-hosted apps → t1k:web:devops:selfhost-cloudflare.

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
”What does `wrangler --install-skills` do?“	wrangler shortcut
”Cloudflare tools aren’t showing up after install”	Verification

Claude Code — skills + MCP in one step

claude plugin marketplace add cloudflare/skills
claude plugin install cloudflare@cloudflare

Then tell the user to run /reload-plugins inside Claude Code to activate the new plugin. Do NOT use npx 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, 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

Skills (any agent supporting the Agent Skills standard):

npx -y skills add cloudflare/skills --skill '*' --yes --global

MCP 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.

`wrangler --install-skills` — skills-only shortcut

wrangler ≥4.112 ships a global flag, --install-skills (“Install Cloudflare skills for detected AI coding agents before running the command”), that can ride along on any wrangler command (e.g. wrangler deploy --install-skills). Verified behavior (wrangler 4.112.0):

Detects installed agents (observed: claude, cursor, opencode, codex, copilot, gemini-cli, kiro-cli, antigravity, junie) and drops the same cloudflare/skills skill files into each one’s skill directory.
Writes a tracking file (~/.config/.wrangler/agents-skills-install.jsonc) so it does not repeat the install on every invocation.
Does NOT register any MCP server — its own output only ever reports skills-install success/failure, never MCP. It is a skills-only shortcut, not a substitute for this skill’s MCP-registration step.
If the flag errors as “unknown option” on a wrangler you can invoke, you likely have wrangler installed under a different nvm-managed Node version than your active shell (npm globals are per-Node-version under nvm) — check with which wrangler / npm ls -g --depth=0 wrangler under the active version, or just use npx -y skills add cloudflare/skills instead, which always fetches fresh regardless of nvm state.

Use it as a convenience for the skills half only; still complete the MCP-registration step above for any agent that needs live Cloudflare account access.

Verification

Claude Code: /reload-plugins, then confirm cloudflare skills/commands appear in the plugin list; first Cloudflare-tool call should prompt OAuth (except cloudflare-docs).
Other agents: re-open the agent’s MCP status/tools panel; cloudflare-docs should connect with no auth prompt, the other 4 should trigger an OAuth flow on first use.

Gotchas

Running the manual npx skills + hand-registered-MCP steps on top of the Claude Code plugin path double-registers the same servers — pick one path per agent, not both.
wrangler --install-skills is skills-only (see above) — do not treat a successful run as MCP being configured too.