返回目錄

dsh-cloudflare-connector

精選清單收錄維護狀態: 活躍

beings-labs/dsh-cloudflare-connector

把 Cloudflare 賬戶接入 dsh 的聯結器外掛,為 agent 與外掛開發者提供統一的訪問入口,省去在每個外掛裡重複配置授權。具體授權範圍與配置步驟以倉庫說明為準。安裝後按說明完成授權即可開始使用。

前往 GitHub
$ dsh plugin add dsh-cloudflare-connector

安裝

dsh 沒有統一的安裝指令 —— 把該外掛 README 中的設定行加入你的 profile / patch 設定,然後重啟即可。

查看安裝教學

4

星數

4

Fork

JavaScript

語言

MIT

授權條款

2026-11-13

建立於

2026-11-15

最近推送

README

@beings-labs/dsh-cloudflare-connector

Listed on dsh-plugin.org

Cloudflare access for DeepSeek Harness agents and plugin developers. Sign in through your browser, use the official MCP tools, or call a typed shared service from your own plugin. No Cloudflare API token to create or manage.

The connector talks to the official Cloudflare API MCP server. It keeps the upstream MCP protocol and tool contracts; the shared plugin API is an additional local integration, not a new server or replacement protocol.

Why use it?

  • Browser sign-in: Cloudflare OAuth with PKCE, using DSH's existing local web server.
  • Agent-ready tools: upstream tools exposed as mcp__cloudflare_connector__*, with their input schemas preserved.
  • Built for plugin developers: one shared connection, public TypeScript types, and direct API requests without nested model-facing tool calls.
  • Explicit permissions: identity and account discovery by default; resource access requires additional browser consent.
  • Persistent sessions: private credential storage, automatic token refresh, and reconnection after restart.

Quick start · Permissions · Configuration · Troubleshooting · Plugin API

Quick start

1. Install in your DSH profile

Install the released package in your DSH profile:

dsh plugin --profile <profile> add @beings-labs/dsh-cloudflare-connector

To use a local development checkout instead, run this from the repository:

npm ci
dsh plugin --profile <profile> add link:/absolute/path/to/dsh-cloudflare-connector

Replace <profile> with the profile you actually run, then restart DSH. This connector uses its own tool, service, callback, and credential namespaces. It is not a drop-in replacement for integrations built around another connector's tools.

Before you start: use Node.js 20 or newer and a DSH 0.2.x Desktop or local Web profile with tools, systemPrompt, and webServer services. Browser OAuth requires a loopback origin; a remotely hosted DSH Web server is not supported. To invoke tools through chat, you also need a working model connection in DSH. That is separate from Cloudflare authorization.

2. Sign in to Cloudflare

Ask your agent:

Call cloudflare_connector_status and cloudflare_connector_authorize.

Open the returned authorizationUrl and approve the requested permissions. The browser callback completes authorization automatically; return to DSH. Never paste API tokens, access tokens, or refresh tokens into chat.

The default grant is:

user:read account:read

This allows identity and account discovery, not access to every Cloudflare resource. Other resource operations may require additional consent. Cloudflare can also grant offline_access for token refresh; status reports the actual granted scopes.

3. Verify with a read-only request

Ask your agent:

Test the Cloudflare connection, then list the accounts I can access. Do not modify any resources.

cloudflare_connector_status should report authorized: true and connected: true; cloudflare_connector_test lists the discovered tools. Upstream tools such as mcp__cloudflare_connector__execute, mcp__cloudflare_connector__whoami, and mcp__cloudflare_connector__search are available when advertised by the server.

If the browser callback cannot reach DSH, call cloudflare_connector_finish with {"code":"<full callback URL>"} through the local DSH tool. A raw code with optional state is also accepted. Callback URLs contain sensitive, short-lived parameters: do not share them in issues, logs, or other chats.

Permissions and authorization

When Cloudflare requests another scope, the connector prepares a consent URL and reports authorization_required or HTTP 403 insufficient_scope.

  1. Call cloudflare_connector_authorize to retrieve the pending URL.
  2. Open it and approve the requested permissions.
  3. Retry the original operation after authorization and reconnection complete.

The connector uses the server's exact challenged scope list and does not automatically replay the refused operation. A plain API 403 without a scope challenge does not start consent automatically. Check the endpoint's documented permissions and availability rather than repeatedly reconnecting with the same grant.

To request a known scope proactively, pass {"scopes":["zone.read"]} to cloudflare_connector_authorize when no flow is pending. Repeated calls during a pending flow return the same URL; they do not change its scopes. Pending flows expire after ten minutes.

Scope names are not inferred from product names or API token permission labels. The connector validates them against the authorization server's scopes_supported discovery metadata when advertised, before registering a client or returning a consent URL. For the default server, inspect its OAuth metadata. Unsupported scopes produce invalid_scope, not a new consent flow. Correct the scope list; reconnecting with the same invalid scope will not help.

authorized means credentials are stored, not that every permission is granted. Pending consent blocks remote calls. To abandon a flow or reduce permissions, run cloudflare_connector_clear and authorize again with the desired configured scopes. Clear deletes local credentials; revoke the upstream grant in Cloudflare separately if needed. Clearing the connector does not sign you out of Cloudflare in your browser.

Agent helper tools

在 GitHub 閱讀完整 README →

DSH Plugins 是獨立的 DeepSeek Harness 外掛目錄,與 DeepSeek 官方無關,也不代表官方背書。第三方外掛未經安全稽核,安裝前請審查原始碼。

每週取得最新的 DeepSeek Harness 外掛,絕不濫發。