dsh-cloudflare-mcp
DeepSeek Harness 的 Cloudflare MCP 连接：通过 mcp.cloudflare.com 使用官方 OAuth 2.0 流程（动态客户端注册 + PKCE）、使用 mcp__cloudflare__* 下的 Cloudflare API 工具，以及网页设置面板
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:zhengjy01/dsh-cloudflare-mcp#e2a32addd2a35f9fa522e2c482ef193f8852dbb7Cloudflare Mcp 以 dsh-cloudflare-mcp 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Cloudflare MCP connection for DeepSeek Harness (DSH): the official Cloudflare API MCP server (mcp.cloudflare.com) with the full OAuth 2.0 client dance — dynamic client registration, PKCE S256, loopback callback on the GUI's own web server, refresh-token grant — plus a web settings panel.
Once authorized, every Cloudflare API tool (accounts, Workers, Pages, DNS,
R2, KV, D1, AI, …) becomes available in agent sessions as
mcp__cloudflare__*, auto-refreshing its token on 401.
DSH's built-in @deepseek-ai/dsh-mcp-client supports static headers only —
it cannot complete the OAuth flow that mcp.cloudflare.com requires
(WWW-Authenticate: Bearer realm="OAuth"). This plugin implements the
OAuth client itself on the official @modelcontextprotocol/sdk primitives,
so the connection is genuinely authenticated, not token-pasted.
# local development (link)
dsh plugin --profile web add link:/path/to/dsh-cloudflare-mcp
The bundle patch mounts the plugin row automatically; a Host restart is
needed for the layer to compose. Tokens live in
~/.dsh/dsh-cloudflare-mcp.json (mode 0600).
Two ways, both starting the same OAuth flow against Cloudflare:
cloudflare_mcp_oauth_start, open the
returned authorizeUrl, or paste the callback code back into
cloudflare_mcp_oauth_finish.Agent-facing helpers (mounted on ctx.tools):
| tool | what it does |
|---|---|
cloudflare_mcp_status | authorization + connection state, tool count (no secrets) |
cloudflare_mcp_oauth_start | begin the OAuth flow, return the browser URL |
cloudflare_mcp_oauth_finish | manual code-paste fallback |
cloudflare_mcp_test | connect and list the MCP server's tools |
cloudflare_mcp_clear | wipe credentials and disconnect |
Plus the MCP server's own tools as mcp__cloudflare__*.
All loopback-only (127.0.0.1), except the OAuth callback which accepts
the cross-site landing from mcp.cloudflare.com while still verifying the
OAuth state:
GET /api/dsh-cloudflare-mcp/statusPOST /api/dsh-cloudflare-mcp/oauth/startGET /api/dsh-cloudflare-mcp/oauth/callback (browser landing)POST /api/dsh-cloudflare-mcp/oauth/finishPOST /api/dsh-cloudflare-mcp/oauth/refreshPOST /api/dsh-cloudflare-mcp/testPOST /api/dsh-cloudflare-mcp/clearpnpm install
npm run typecheck
npm run test # offline store/provider smoke
DSH_CLOUDFLARE_MCP_LIVE=1 npm run test # live OAuth phase-1 against mcp.cloudflare.com
npm run build # tsc declarations + tsdown (lib/ + lib/client.js)
MIT