deepseekplugins

DeepSeek Harness plugin

dsh-mcp-management

DeepSeek Harness profile bundle for MCP connection management in Web Settings

Tools & Capabilities
Jump to install

Source facts

Repository
anht3889/dsh-mcp-management
Latest update
Aug 21, 2026
Category
Tools & Capabilities
GitHub stars
1
Format
plugin
Package path
packages/bundle
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
packages/bundle/package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/anht3889/dsh-mcp-management/tree/HEAD/packages/bundle
Plugin: dsh-mcp-management
Author: anht3889

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer2 files
README.mdSource · read only

dsh-mcp-management

Out-of-tree MCP connection management for DeepSeek Harness. Architecture and scope live in docs/design.md.

Install

From npm (after the packages are published):

npx @deepseek-ai/dsh plugin --profile web add @anht3889/dsh-mcp-mgmt-bundle@0.0.5

From a local checkout (development):

pnpm install && pnpm run build
npx @deepseek-ai/dsh plugin --profile web add ./packages/bundle

Restart the Web profile after installation.

Do not also mount @deepseek-ai/dsh-mcp-client for the same serverName — both register MCP tools and will conflict.

Settings UI

Add a server. Open Settings → MCP Servers and choose Add server. Fill in the name, transport (stdio or HTTP), command or URL, and authentication, then Save. Timeout and reconnect options live under Advanced settings.

!Add MCP server

Server list. Each row shows the server name, an Enabled switch, and a summary of transport, connection state, and how many tools are enabled. Authorize appears only while an OAuth server has no token. Click the row to open details.

!MCP Servers list

Server details. Toggle the server or individual tools, Reload to reconnect and re-list tools, open Connection logs, or use Edit configuration, Log out, and Delete. Disabling a tool unregisters it without dropping the connection; the choice is stored in the server record and survives a restart.

!MCP server details

Storage

DataDefault path
Non-secret server records, including disabled tool names~/.dsh/mcp/servers.json
Secrets (tokens, header values, client secret)~/.dsh/mcp/secrets.yaml, or ctx.credentials when mounted

Override with the manager plugin's catalogPath / secretsPath config.

Servers behind a private certificate authority

Node trusts only its own bundled certificate authorities, so an HTTP server whose certificate comes from a corporate CA fails to connect with self-signed certificate in certificate chain even though a browser or curl reaches it. Set trustSystemCertificates: true on the manager plugin to trust the host's authorities as well, or launch the host with NODE_OPTIONS=--use-system-ca. Both widen TLS trust for the whole host process, which is why the config stays off by default.

OAuth

Each server's callback URL is the live web origin plus that server's auth.redirectPath (default /callback). Set publicOrigin on the manager when the browser reaches the host through a different origin. Authorization servers match the redirect URI exactly; a pre-registered public client usually allows /callback on any loopback port. The manager serves every configured path. Authorize and token requests also send the MCP URL as the RFC 8707 resource indicator.

Packages

PackageRole
@anht3889/dsh-mcp-mgmt-bundleInstallable surface: patch, manager, Settings UI
@anht3889/dsh-mcp-mgmt-mcpctx.mcp vocabulary (library)
@anht3889/dsh-mcp-mgmt-oauthPKCE OAuth + discovery (library)

License

[MIT](LICENSE)

Back to searchOpen GitHub repository

More related plugins

View category