hyqhyq3/dsh-mcp-manager
MCP server manager plugin for DeepSeek Harness: Settings → MCP page, OAuth (PKCE + dynamic client registration
dsh-mcp-manager is an MCP server manager for DeepSeek Harness — a Settings → MCP page where you add MCP servers once (remote HTTP or local stdio process), authenticate HTTP servers with OAuth in the browser (authorization code + PKCE, RFC 7591 dynamic client registration, refresh_token rotation, auto-reconnect across restarts), and expose their tools directly or through a compact on-demand broker. It fills the gap where the built-in @deepseek-ai/dsh-mcp-client only accepts static headers: static Bearer token mode stored as an environment-variable name (Codex-style tokenEnv), custom HTTP headers (headers / headerEnv), stdio local processes (npx / uvx / python etc. with JSON-RPC over stdin/stdout), edit-in-place, tool registration with the mcp<server><rawName> convention plus strict-schema sanitization, workspace isolation via <workspace>/.dsh/dshmm/mcp.json with per-workspace masking, an opt-in on-demand broker (mcp_search_tools / mcp_describe_tool / mcp_execute_tool), and stable tool refresh via notifications/tools/list_changed.
Install
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:hyqhyq3/dsh-mcp-managernpx -p @deepseek-ai/dsh dsh plugin --profile web add github:hyqhyq3/dsh-mcp-manager, then restart dsh --profile web and refresh the page. The package declares a dsh.bundle.patch, so the plugin activates automatically — no manual cordis.patch.yml editing. Requirements: DeepSeek Harness with the web profile, Node.js ^22.19 or >=24, pnpm on PATH; Windows 10/11 stdio commands launch via cmd.exe so .cmd shims resolve.
Compatibility
DeepSeek Harness web profile (npx @deepseek-ai/dsh web); Node.js ^22.19 or >=24; pnpm on PATH; Windows 10/11 supported (cmd.exe for .cmd shims). OAuth requires the MCP provider to allow a loopback redirect (http://127.0.0.1:<port>/mcp-manager/callback/<id>).
Details
- Repo: hyqhyq3/dsh-mcp-manager
- Category: Plugin Markets & Managers
- Stars: 10
- Version: npm package dsh-mcp-manager 0.6.0 (registry-verified 2026-08-23); MIT
- Last push: 2026-09-11
- First seen: 2026-08-13
Recent updates
The current README documents the feature list, requirements, install, usage (Settings → MCP, add server with scope user/workspace, HTTP vs stdio, OAuth flow), limitations (no resources/prompts bridging, on-demand filtering targets the native presentation, OAuth tokens in a plain JSON file under ~/.dsh), and the MIT license.
FAQ
- Does it support OAuth-protected MCP servers?
- Yes — authorization code + PKCE with RFC 7591 dynamic client registration, refresh_token rotation, and auto-reconnect across restarts; one browser login and it keeps working.
- Can I run local stdio MCP servers?
- Yes — npx / uvx / python etc. run directly as child processes speaking JSON-RPC over stdin/stdout; Windows .cmd shims are resolved through cmd.exe.
- Are workspace-scoped servers isolated?
- Yes — declare per-project servers in <workspace>/.dsh/dshmm/mcp.json and their tools register only into that workspace's sessions; you can also mask specific global servers per workspace.
Alternatives
omdsh-dev/dsh-at-file · linyp/dsh-plugin-langfuse · omdsh-dev/dsh_workflow