DSH Plugin HubDSH 插件市场
hyqhyq3/dsh-mcp-manager 预览 preview

hyqhyq3/dsh-mcp-manager

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

DeepSeek Harness 的 MCP 服务器管理器插件：设置 → MCP 页面，支持 OAuth（PKCE + 动态客户端注册）或静态令牌认证，工具注册为 mcp__<name>__* 格式。

Project Overview项目介绍

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

dsh-mcp-manager is a native plugin for DeepSeek Harness (DSH) that adds full MCP server management capabilities to the DSH platform. It fills the gap left by DSH’s built-in MCP client, which only supports static header configuration and lacks OAuth authentication and local stdio transport support. To install the plugin, you can run the official DSH CLI command npx -p @deepseek-ai/dsh dsh plugin --profile web add github:hyqhyq3/dsh-mcp-manager, then restart your DSH web profile and refresh the settings page to access the new MCP management interface. The plugin automatically activates after installation because it includes a pre-configured DSH bundle patch, so you don’t need to manually edit any cordis configuration files.

This plugin is built for DSH users who need to connect to external MCP servers to extend DSH’s native tool capabilities. It supports three different authentication flows to match different MCP server requirements: OAuth 2.0 with authorization code and PKCE for remote servers that require login, static Bearer token for servers that use pre-shared tokens, and no authentication for open local or remote servers. You can edit existing server configurations in place without deleting and re-adding them, which makes adjusting server settings much faster and more convenient. It also supports workspace isolation so you can declare project-specific MCP servers that only load when you are working on that specific workspace.

The plugin relies on DSH’s existing locale system, so it automatically follows DSH’s global language preference set in the General Settings page, and no extra language configuration is required from users. To run the plugin you need Node.js version 22.19 or newer, and it has been verified to work stably with DSH versions from 0.1.2-rc.1 up to before 0.2.0. Currently, the plugin only bridges MCP tool capabilities, and does not yet support MCP resources or prompts functionality. OAuth access tokens are stored as plaintext in a JSON file under your DSH home directory, so you should treat that file as sensitive information to avoid credential leaks.

这是一款专为 DeepSeek Harness (DSH) 开发的原生 MCP 服务器管理插件，它在 DSH 的网页设置界面中新增了专门的 MCP 管理页面，支持添加本地 stdio 进程和远程 HTTP 两种类型的 MCP 服务器，补充了 DSH 内置 MCP 客户端缺少的 OAuth 认证功能，并且沿用了内置客户端的工具命名规范，可以和 DSH 的工具注册表无缝集成。

面向需要使用 MCP 服务器的 DSH 用户，它支持多种认证方式，包括带 PKCE 的授权码 OAuth 流程、静态 Bearer 令牌模式以及无认证模式，还支持自定义 HTTP 请求头，可直接编辑现有服务器配置，支持工作区隔离，还提供可选的按需代理模式优化模型请求体验。

插件遵循 DSH 的全局语言设置，不需要额外配置语言选项，安装需要 Node.js 22.19 以上版本，支持 DSH 0.1.2-rc.1 到 0.2.0 之间的版本，仅对 MCP 工具能力做桥接，暂不支持 MCP 的资源和提示功能，OAuth 令牌以明文 JSON 形式存储在用户目录下，需要注意保密。

View on GitHub在 GitHub 查看

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

插件：dsh-mcp-manager（hyqhyq3/dsh-mcp-manager）
仓库：https://github.com/hyqhyq3/dsh-mcp-manager
本站详情页：https://www.yhbd.top/plugins/hyqhyq3-dsh-mcp-manager/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 20 · 最近提交 2026-09-11 · 主语言 JavaScript

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

【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 note1 项提示
  • 20 stars - an early-stage project星标 20，属于早期项目
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:hyqhyq3/dsh-mcp-manager

把 hyqhyq3/dsh-mcp-manager 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

17.4 KB · 缓存于 2026-09-11 19:39:49 · 17.4 KB

dsh-mcp-manager

简体中文 | English

MCP server manager for DeepSeek Harness (DSH) — a Settings → MCP page where you add MCP servers once (remote HTTP or local stdio process), authenticate HTTP servers with OAuth in the browser, and expose their tools either directly or through a compact on-demand broker.

The built-in @deepseek-ai/dsh-mcp-client only accepts a static headers config — it has no OAuth support and no local stdio transport. This plugin fills that gap:

  • OAuth (authorization code + PKCE) with RFC 7591 dynamic client registration, refresh_token rotation, and auto-reconnect across restarts — one browser login, then it keeps working.
  • Static Bearer token mode for servers without OAuth — stored as an environment-variable name (Codex-style tokenEnv), never as plaintext in the config.
  • No auth mode for servers that need no credentials at all (e.g. a local http://127.0.0.1:9316/mcp) — the plugin sends no Authorization header and connects on save.
  • Custom HTTP headers (headers for direct values, headerEnv for values read from environment variables) — matches Codex's http_headers / env_http_headers.
  • stdio local processes: run npx / uvx / python etc. directly; the plugin speaks JSON-RPC over the child's stdin/stdout (spawns the process, reconnects, and reaps it on exit) — no remote server or auth required. Windows .cmd shims (e.g. npx.cmd) are resolved through cmd.exe.
  • Edit-in-place: rename a server, switch stdio ↔ HTTP, or change auth/headers without deleting and re-adding it.
  • Tool registration with the same mcp__<server>__<rawName> naming convention as the built-in client, including strict-schema sanitization for the DSH tool registry and isConcurrencySafe marking.
  • Workspace isolation: declare per-project servers in <workspace>/.dsh/dshmm/mcp.json — their tools register only into that workspace's sessions, and you can mask specific global servers per workspace.
  • Opt-in on-demand broker: keep the model-facing MCP surface fixed at mcp_search_tools, mcp_describe_tool, and mcp_execute_tool instead of sending every mcp__* schema on every Native-mode request. It is disabled by default. mcp_search_tools is a zero-dependency lexical ranker (BM25 + CJK/alias/fuzzy, plus a catalog-listing fallback).
  • Stable tool refresh: notifications/tools/list_changed refreshes only added, removed, or schema-changed registrations for both stdio and Streamable HTTP servers.

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

渲染基于仓库 hyqhyq3/dsh-mcp-manager 的 README.md。 在 GitHub 查看原文 →

Related相关推荐

← 上一个 Prev dsh-tui 下一个 Next dsh-skin →