ChatGPTClaudeGrok / X / CursorGemini

dsh-cloudflare-connector: Token-Free Cloudflare Access for DeepSeek Harness

beings-labs/dsh-cloudflare-connector

Integrations & ConnectionsVerified
Listed on 2026-11-15
Page last updated 2026-11-15

Cloudflare access for DeepSeek Harness agents and plugin developers: browser OAuth sign-in and official Cloudflare MCP tools, with no API token to manage.

dsh-cloudflare-connector is a Cloudflare access plugin for DeepSeek Harness that lets agents and plugin developers use Cloudflare without creating or managing API tokens. It signs in through browser OAuth against the official Cloudflare API MCP server, keeps the upstream MCP protocol and tool contracts intact, and adds a shared local plugin API on top. Identity and account discovery are granted by default, other resources require fresh browser consent, and credentials are stored privately with automatic token refresh and reconnection after a restart.

How to Install

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

Replace --profile with the profile name you actually run (see ls ~/.dsh/profiles/): usually web in the browser UI, desktop or desktop-NNN in the desktop app.

Category
Integrations & Connections
Platform
DSH Plugin
Author
beings-labs
Distribution
Plugin

dsh-cloudflare-connector Key Features

Browser OAuth sign-in, no API tokenOfficial MCP tools exposed directlyShared connection for other pluginsExplicit, consent-based permissionsPersistent credentials with auto refresh
Listed on dsh-plugin.org

dsh-cloudflare-connector Repo Summary

What Does It Do?

Cloudflare Connector is a DSH plugin for DeepSeek Harness that gives agents and plugin developers access to Cloudflare without creating or managing an API token. It signs in through browser-based OAuth against the official Cloudflare API MCP server, keeps the upstream MCP protocol and tool contracts intact, and adds a shared local plugin API on top. It solves the credential-management and coarse-permission problem: identity and account discovery are granted by default, while resource access needs additional consent. It is maintained by beings-labs under the MIT license and written in JavaScript.

Core Features

  • Browser sign-in: Cloudflare OAuth with PKCE that reuses DSH's existing local web server for the callback, so no token is ever pasted into chat.
  • Agent-ready tools: upstream tools are exposed as mcp__cloudflare_connector__* with their input schemas preserved, covering execution, identity, and search operations.
  • Shared connection for plugin developers: one connection is reused across callers, with public TypeScript types and direct API requests that avoid nested model-facing tool calls.
  • Explicit permissions: the default grant is user:read account:read for identity and account discovery only; other resource operations return authorization_required or HTTP 403 insufficient_scope until the user consents in the browser.
  • Persistent sessions: credentials are stored privately, tokens refresh automatically, and the connection re-establishes after a restart.

How to Use This Plugin?

After enabling it in a DSH Desktop or local Web profile, ask the agent to call the status and authorize tools, open the returned authorizationUrl, and approve the requested permissions; the browser callback completes authorization automatically. Then run a read-only check: test the connection and list accessible accounts, and the status tool should report authorized and connected. If the browser callback cannot reach DSH, finish authorization by submitting the code through the local tool instead; callback URLs carry sensitive short-lived parameters and should not be shared in logs or chats. When more scopes are needed, fetch the pending consent URL, approve it, and retry the original operation.

How to Troubleshoot This Plugin?

An authorization_required or HTTP 403 insufficient_scope response means the current grant is too narrow: start authorization again, approve the requested permissions as described in the official docs, and retry the operation. If the browser callback cannot reach DSH, submit the authorization code through the local tool to complete the flow. When status reports not connected, confirm the DSH version and required services match the documented requirements, and check that a loopback origin is used rather than a remotely hosted web server.

This page is an independent rewrite of the plugin's official README — for authoritative documentation and the latest changes, refer to the source: beings-labs/dsh-cloudflare-connector. The plugin is third-party code that runs on your machine once installed; inclusion does not imply endorsement — please review the source before installing.

Install, update, and uninstall this plugin in the Plugin Market of DeepSeek Harness's DSH Plugin Hub
ChatGPTClaudeGrok / X / CursorGemini

DSH Plugin FAQ