beings-labs/dsh-cloudflare-connector ↗★ 4
@beings-labs/dsh-cloudflare-connector
Shared Cloudflare access for DeepSeek Harness agents and plugins, using official MCP tools and browser OAuth.
安裝
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:beings-labs/dsh-cloudflare-connector說明文件
閱讀完整 README ↗Configuration
Defaults work without configuration. To customize the connector, edit your
profile's cordis.patch.yml:
- id: beings-labs-cloudflare-connector
config:
enabled: true
announceToAgent: true
scopes:
- user:read
- account:read
# tokenFile: /absolute/path/to/private/auth.json
| Option | Default | Purpose |
|---|---|---|
enabled | true | Enable tools, service, callback, and guidance |
announceToAgent | true | Include authorization guidance in the agent's prompt |
scopes | user:read account:read | Replace the initial scope list |
endpoint | https://mcp.cloudflare.com/mcp | MCP endpoint; HTTPS required except loopback development |
tokenFile | Default private path below | Absolute path for stored OAuth credentials |
Credentials default to $DSH_HOME/dsh-cloudflare-connector/auth.json, or
~/.dsh/dsh-cloudflare-connector/auth.json when DSH_HOME is unset. Files use mode
0600, with private directories created as 0700. Never commit or share them.
Concurrent profiles should use separate tokenFile paths.
Credentials are bound to the configured endpoint. To change endpoints, use a different credential file or remove the old one and authorize again.
Only install plugins you trust: consumers share the authorized Cloudflare access. Authorizing or clearing credentials affects all consumers in the profile. The connector does not enforce read-only access or approval policies for your agent.