Skip to content

☁️ Cloudflare MCP Servers

Status: ✅ Installed & Configured | Last setup: 2026-04-20

Three remote Cloudflare MCP servers give Copilot CLI direct access to your Cloudflare account — Pages deployments, Workers, DNS, cache, builds, logs, and analytics — all without leaving the terminal.

Quick Reference

Item Value
Server type Remote HTTP (no local install)
Auth type OAuth2 (Cloudflare, via browser)
Config file ~/.copilot/mcp-config.json
Account Susanth.ss@gmail.com
Account ID d42846fe2c29daf890ec57877fda5e04

MCP Servers

Server URL Purpose
cloudflare-code https://mcp.cloudflare.com/mcp Full API access — 2,500+ endpoints via search + execute tools
cloudflare-builds https://builds.mcp.cloudflare.com/mcp Deploy status, build logs, retry failed deploys
cloudflare-observability https://observability.mcp.cloudflare.com/mcp View logs, errors, analytics

Other Available Servers (not installed)

Server URL Purpose
DNS Analytics https://dns-analytics.mcp.cloudflare.com/mcp DNS performance debugging
Docs https://docs.mcp.cloudflare.com/mcp Search Cloudflare documentation

What It Can Do

Capability Example Command
📋 List Pages projects "List my Cloudflare Pages projects"
🚀 Deploy status "Latest deploy status for aguidetocloud-revamp"
🧹 Cache purge "Purge cache for aguidetocloud.com/guided/"
🌐 DNS management "Show DNS records for aguidetocloud.com"
👷 Workers "List my Workers"
📊 Analytics "Show traffic analytics for last 7 days"
📝 Build logs "Show build logs for latest deploy"
🔍 API search Searches 2,500+ Cloudflare API endpoints
⚡ Execute API Runs any Cloudflare API call directly

Pages Projects

Project Subdomain Branch Custom Domain
aguidetocloud-revamp aguidetocloud-revamp.pages.dev main aguidetocloud.com
learning-portal learning-portal-acd.pages.dev main learn.aguidetocloud.com
guided guided-49q.pages.dev main —

Setup History

Initial Setup (2026-04-20, Session 0dd31fad)

  1. Guide followed: ~/.copilot/session-state/a49eb4bc-c806-48f9-b9aa-cdb6ee24ae80/files/cloudflare-mcp-setup.md
  2. Added 3 servers to ~/.copilot/mcp-config.json: 
    "cloudflare-code": {
  "type": "http",
  "url": "https://mcp.cloudflare.com/mcp"
},
"cloudflare-builds": {
  "type": "http",
  "url": "https://builds.mcp.cloudflare.com/mcp"
},
"cloudflare-observability": {
  "type": "http",
  "url": "https://observability.mcp.cloudflare.com/mcp"
}
  3. Added Cloudflare URLs to allowedUrls in ~/.copilot/config.json
  4. OAuth authorized via browser popup — tokens cached automatically
  5. Verified — successfully listed all 3 Pages projects

How It Works

Unlike the YouTube or M365 MCP servers (which run locally via node), Cloudflare's MCP servers are remote:

Copilot CLI → HTTPS → mcp.cloudflare.com → Cloudflare API → Your Account
  • No local process — nothing to install, update, or restart
  • OAuth tokens cached — browser auth only needed on first use
  • Two tools power the Code server:
    • cloudflare-code-search — search the OpenAPI spec to find the right endpoints
    • cloudflare-code-execute — run JavaScript against the Cloudflare API

Troubleshooting

OAuth Expired?

If you get an auth error, the OAuth session may have expired. Copilot CLI will automatically prompt browser re-auth on next use.

MCP Server Not Loading?

  1. Check it's in your config: Get-Content ~/.copilot/mcp-config.json
  2. Restart Copilot CLI (/exit then relaunch)
  3. Run /mcp to verify servers show up
  4. Test with: "List my Cloudflare Pages projects"

Adding More Servers

Add to ~/.copilot/mcp-config.json using the same type: "http" format. Available servers listed at developers.cloudflare.com/mcp.

References