dsh-cloudflare-connector
キュレーションリスト掲載メンテナンス: 活発beings-labs/dsh-cloudflare-connector
DeepSeek Harness のエージェントとプラグイン開発者向けの Cloudflare アクセス連携。Cloudflare 側の資源や API を DSH から扱いやすくする。
$ dsh plugin add dsh-cloudflare-connector4
スター
4
フォーク
JavaScript
言語
MIT
ライセンス
2026-11-13
作成日
2026-11-15
最終プッシュ
README
@beings-labs/dsh-cloudflare-connector
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.
- Call
cloudflare_connector_authorizeto retrieve the pending URL. - Open it and approve the requested permissions.
- 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
プラグイン開発ツール の他のプラグイン
dsh-context
by bowenliang123
モデルのコンテキストウィンドウ構成と推移を可視化する Context ダッシュボード/コマンド
deepseek-harness-control-center
by feibi-mochi
DSH Web コントロールセンター:アカウント監視、用量、完了アラート、公式チャージ、柔軟レイアウト、agent 支援セッション制御
dsh-context-doctor
by zhenyu98
DSH コンテキスト注入監査:AGENTS.md/スキル/ツール schema/MCP の token コストと重複・shadow 衝突検出
dsh-balance-plugin
by yxxbc
DeepSeek の残高監視と利用量統計をする DSH 動的 Cordis プラグイン。残高監視・公式チャージ入口・利用量統計・サードパーティプラグイン管理を一本化します。
