DSH Plugin HubDSH 插件市场
springbrand-lab/dsh-oauth-mcp-client 预览 preview

springbrand-lab/dsh-oauth-mcp-client

Plugin插件 Native原生 ⭐ 8 MIT Models & Routing模型与路由

DeepSeek Harness 的 OAuth 2.1 可流式 HTTP MCP 客户端插件。

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

This is a native DSH plugin that provides an OAuth 2.1-enabled Streamable HTTP MCP client for DeepSeek Harness. It extends DSH’s native dsh-mcp-client with additional authentication and connection management features, including PKCE validation, dynamic client registration, browser-based authorization, and automatic reconnect handling. To install the plugin, you first clone the repository, install dependencies with pnpm, build the package, then add the built local checkout to your DSH web profile via the DSH CLI. The default bundled configuration connects directly to Springbrand’s production MCP gateway, so no extra MCP registration step is needed after installation.

After installation and first startup, your browser will open automatically to complete Springbrand login and OAuth consent. To use the plugin, you just send a natural language request to search the Springbrand capability catalog for the resource or service you need. The plugin automatically adds tool calling guidance to the DSH agent, so the agent will first search for matching capabilities, then call the execution tool with the full capability name returned from the search. You can also manually add new custom OAuth-enabled MCP Streamable HTTP connections through the DSH Web settings UI.

The plugin requires Node.js 22.19 or later, Git, and a working web browser to complete first-time OAuth login. It stores OAuth tokens and client metadata through DSH’s built-in credential service, and the OAuth callback listener only binds to the local loopback interface for security. The project is released under the open-source MIT license, with core portions of the code adapted from DeepSeek Harness’s native @deepseek-ai/dsh-mcp-client module, also under the MIT license. All connection configurations are stored permanently in your DSH profile directory, so connections persist across DSH restarts without reconfiguration.

这是一个专门为DeepSeek Harness开发的原生插件，是支持OAuth 2.1协议的可流式HTTP MCP客户端。它扩展了DSH原生dsh-mcp-client的连接流程，增加了PKCE验证、动态客户端注册、浏览器授权、环回回调、持久令牌存储、自动重连处理和MCP工具自动注册功能，默认配置连接Springbrand官方生产级MCP网关，可通过一键安装完成持久化连接配置，由SpringBrand团队维护。

用户可以通过这个插件调用Springbrand市场提供的各类AI商业服务能力，典型工作流是：用户先请求搜索Springbrand能力目录，获取完整的能力名称后，再调用执行能力接口得到最终结果。插件会自动给Agent添加工具调用规范指南，用户只需正常发送自然语言请求，无需手动调用工具，还可手动添加其他支持OAuth的MCP服务器连接。

插件要求Node.js 22.19及以上版本和Git，首次使用需要通过浏览器完成OAuth登录授权。安装方式为克隆仓库后本地构建，再添加到DSH配置文件中，连接信息会永久保存在用户的DSH配置目录中，重启DSH后依然保留。本项目采用MIT许可协议，部分核心代码源自DeepSeek Harness的原生MCP客户端模块。

View on GitHub在 GitHub 查看

Recommended强烈推荐 Send to your DSH发给你的 DSH 安装 
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-oauth-mcp-client（springbrand-lab/dsh-oauth-mcp-client）
仓库：https://github.com/springbrand-lab/dsh-oauth-mcp-client
本站详情页：https://www.yhbd.top/plugins/springbrand-lab-dsh-oauth-mcp-client/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 8 · 最近提交 2026-08-14 · 主语言 TypeScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意
  • Only 8 stars - very few users, little community feedback星标只有 8，几乎没人在用，遇到问题缺少社区反馈
DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

  • DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
  • External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
  • Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

  • Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
  • Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
  • curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
  • Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
  • Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
  • Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装 

dsh plugin --profile web add github:springbrand-lab/dsh-oauth-mcp-client

把 springbrand-lab/dsh-oauth-mcp-client 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

6.2 KB · 缓存于 2026-08-23 03:41:21 · 6.2 KB

dsh-oauth-mcp-client

English | 简体中文

An OAuth 2.1 Streamable HTTP MCP client plugin for DeepSeek Harness.

It extends the native dsh-mcp-client connection flow with PKCE, dynamic client registration, browser authorization, a loopback callback, persistent token storage, reconnect handling, and MCP tool registration. The bundled configuration connects to the Springbrand production MCP Gateway.

This plugin is maintained by SpringBrand, an AI-assisted marketplace for business services. See the SpringBrand DeepSeek Harness page for product information.

Features

  • OAuth 2.1 authorization code flow with PKCE
  • Dynamic OAuth client registration
  • Browser login with a loopback callback
  • Token and client metadata storage through the DSH credential service
  • Streamable HTTP transport with automatic reconnects
  • MCP tool discovery, registration, and execution
  • DSH Web connection management with live status and capability discovery
  • One-click persistent connection setup followed by browser OAuth

Requirements

  • Node.js 22.19 or later
  • Git
  • A browser for the first OAuth login

Install

Clone and build the plugin:

git clone https://github.com/springbrand-lab/dsh-oauth-mcp-client.git
cd dsh-oauth-mcp-client
corepack enable
pnpm install
pnpm build

Install the built checkout into a DSH profile and start DSH:

PLUGIN_DIR="$PWD"
npx --yes @deepseek-ai/dsh@latest plugin --profile web add "$PLUGIN_DIR"
npx --yes @deepseek-ai/dsh@latest web

This repository is not published to npm, so installation currently uses the local checkout. Adding the bundle to the profile also adds the bundled Springbrand MCP connection; there is no separate MCP registration step.

The first startup opens a browser for Springbrand login and consent. After authorization, open Settings → Plugins → MCP Connections to see the live connection status and registered capabilities. You can also use these tools to verify the bundled connection:

  • mcp__springbrand__search_capabilities
  • mcp__springbrand__execute_capability

Use

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 springbrand-lab/dsh-oauth-mcp-client 的 README.md。 在 GitHub 查看原文 →

Related相关推荐

← 上一个 Prev dsh-bash-encoding 下一个 Next poe2-exile-architect →