dsh-cloudflare-mcp

DSH's built-in MCP client only supports static request headers, but the official Cloudflare MCP server (mcp.cloudflare.com) demands a full OAuth 2.0 flow—dynamic client registration, PKCE S256, loopback callback, and refresh-token grant—that a plain header approach simply cannot complete. This plugin implements the OAuth client on top of the official @modelcontextprotocol/sdk, so the connection is genuinely authenticated rather than a pasted token pretending to work.

Once authorized, every Cloudflare API tool—Accounts, Workers, Pages, DNS, R2, KV, D1, AI, and more—appears in your agent sessions as mcp__cloudflare__* with automatic token refresh on 401 and no manual intervention. You can authorize through the Web settings panel with a single click that opens Cloudflare's consent page, or right from the chat by having the agent kick off the OAuth flow and pasting the callback code back. Both paths follow the same underlying flow.

If you are a DSH user who regularly manages Cloudflare resources—deploying Workers, tweaking DNS records, checking R2 usage, or running AI inference—this plugin removes the friction of hand-crafting API requests and repeatedly refreshing tokens, turning your agent session into a genuine Cloudflare control panel.