cloudflare_skill

Overview

This skill deploys and manages Cloudflare Workers, Pages sites, and MCP servers to accelerate agentic AI infrastructure. It automates common deployment flows, enforces required environment handling, and provides troubleshooting for auth and deployment errors. Use it to reliably push Workers or Pages and to diagnose token-related failures.

How this skill works

Before performing any action the skill issues a local voice notification and a text notification announcing the workflow and intent. It inspects environment variables (CF_API_TOKEN, CLOUDFLARE_API_TOKEN) and will unset them where they interfere with wrangler OAuth login, then runs the appropriate wrangler commands to deploy Workers, Pages, or MCP servers. Troubleshooting workflows detect token overrides and other auth issues and guide a fix-and-redeploy flow.

When to use it

• Deploy a Cloudflare Worker or MCP server to workers.dev
• Deploy a Cloudflare Pages static site from a built dist/ directory
• Troubleshoot authentication or deployment failures related to tokens
• Automate repeated deploys while ensuring correct OAuth flow
• When wrangler login-based auth is required instead of API tokens

Best practices

• Always run the skill with the expected CF_ACCOUNT_ID environment variable set
• Unset CF_API_TOKEN and CLOUDFLARE_API_TOKEN before Worker deploys to avoid auth conflicts
• Always unset all API tokens before Pages deploys; use wrangler OAuth login
• Build your dist/ output locally before invoking a Pages deploy
• Use descriptive project and worker names to form predictable worker URLs

Example use cases

• Create an MCP server: unsets tokens, runs wrangler deploy, returns the workers.dev URL
• Deploy a Pages site: build dist/, unset tokens, run npx wrangler pages deploy --project-name=PROJECT_NAME --commit-dirty=true
• Fix auth errors: run the troubleshoot workflow, identify token interference, unset tokens and retry
• Automated CI step that clears tokens and invokes wrangler login-based deploy