DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
← Plugins
P

@royenheart/dsh-plugin-mcp-support

Plugin Mcp Support

Thin, non-duplicating dsh wrapper over the native @deepseek-ai/dsh-mcp-client bridge: composition- and settings-driven MCP server mounts.

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add github:royenheart/dsh-plugin-mcp-support#c4eb7dceeddae0c3a3c9813a5e18a1bcc6991333
READMECompatibilityVersions

Compatibility and provenance

Plugin Mcp Support is published as @royenheart/dsh-plugin-mcp-support and currently resolves to version 0.1.0. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
web
Release source
github
Registry updated
8/25/2026

Versions

0.1.0stable
8/25/2026

Related plugins

Loading related plugins…

Latest
0.1.0
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
Unavailable
Files
Unavailable
Surface
web
License
MIT
Source
github
GitHub
★ 0
Weekly downloads
0
Last push
9/22/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue

Related plugins

More verified plugins in integrations-communication.

Acp App@deepseek-ai/dsh-acp-appThe dsh ACP profile bundle: automation-only JSON-RPC stdio and process lifecycle over dsh-baseDs Botds-botDS Bot: a team of long-lived Bots for DeepSeek Harness, with Main Bots, Bot-to-Bot messages and group chatsFree Searchdsh-free-searchFree web search for DeepSeek Harness: 42 engines (Bing/DuckDuckGo/AnySearch/SearXNG/Exa/Tavily/Keenable/Firecrawl/Parallel/Brave/Zhipu/You.com keyless; Zhihu global/site via MCP and Perplexity/SerpBase/DeepSeek (official + native tools/search)/Baidu/Kimi/Ab Publishdsh-ab-publishBrowser-automation publishing tool that logs into and posts to arbitrary websites, in one publishable plugin package

README

@royenheart/dsh-plugin-mcp-support

A thin, non-duplicating wrapper over the native dsh MCP bridge @deepseek-ai/dsh-mcp-client. It makes MCP servers configurable through two layered sources:

  1. Composition config — the plugin entry's servers list.
  2. Persisted dsh settings — the mcp-support settings namespace.

The wrapper mounts one native mcp-client child fiber per effective server and re-syncs the mounted set whenever the settings section changes. It does not vendor or re-implement any connection, tool-discovery, or reconnect logic.

Layout

src/index.ts          # host plugin: settings registration + dynamic child mounts + status route
src/client/index.ts   # browser half: "mcp" view tab (status page)
src/core/config.ts    # pure normalize/merge helpers (no cordis imports)
src/core/status.ts    # pure status-row shaping helper
tests/                # node:test suite using a real cordis Context
lib/                  # built host + client entries (npm run build)

Web status view

The client half registers an mcp tab in the session header's view-tab row, immediately to the right of the 轨迹 (trajectory) tab and before any later tabs such as 技能. Selecting it fetches /plugins/@royenheart/dsh-plugin-mcp-support/status and shows each effective MCP server with its transport, mounted state, and the last mount error when present. No servers configured renders "No MCP servers configured."

Install into a profile

lib/ is generated locally and is not committed. install.py always builds the repository's own toolchain first (npm install when the toolchain is missing, then npm run build) and only reports an error when npm itself is missing.

Install/uninstall idempotently with the bundled script (stdlib-only Python). The package ships its own cordis.patch.yml (id mcp-support) and declares dsh.bundle.patch, so the script only links the package into the profile node_modules, adds the link: dependency, and appends the package to dsh.profile.bundles. The profile's own cordis.patch.yml is never modified:

python3 install.py install --profile web          # install
python3 install.py uninstall --profile web        # remove
python3 install.py install --profile web --home "$DSH_HOME"   # explicit home

Manual alternative:

dsh plugin --profile <profile-name> add link:/home/royenheart/projects/dsh-plugins/dsh-plugin-mcp-support

dsh plugin reconciles dsh.profile.bundles from the installed package's dsh.bundle declaration, so no profile patch edit is needed either.

Restart dsh. The plugin declares inject: ['settings', 'tools'], so it loads once both the dsh settings service and the native tool registry are available.

Composition config example

Configure the bundle-inserted row by id in the profile's own cordis.patch.yml (the bundle patch already inserts the row; this patch only overrides its config):

- id: mcp-support
  config:
    servers:
      - transport: stdio
        serverName: filesystem
        command: npx
        args:
          - -y
          - '@modelcontextprotocol/server-filesystem'
          - /tmp
        env: {}
        cwd: ''
        toolCallTimeoutMs: 60000
        failOnStartupError: false

      - transport: streamable-http
        serverName: everything
        url: http://localhost:3000/mcp
        headers:
          Authorization: Bearer secret
        toolCallTimeoutMs: 60000
        failOnStartupError: false

Settings example

Persisted settings are layered over the composition list. Servers are keyed by serverName: a settings server with the same name overrides the composition entry; settings-only servers are appended after composition servers.

The namespace is mcp-support. (If settings.yaml still carries the key from an earlier misspelled build, rename that key to mcp-support once.)

In the profile's settings document (settings.yaml):

mcp-support:
  servers:
    - transport: stdio
      serverName: filesystem
      command: npx
      args:
        - -y
        - '@modelcontextprotocol/server-filesystem'
        - /tmp

    - transport: streamable-http
      serverName: everything
      url: http://localhost:3000/mcp
      headers:
        Authorization: Bearer secret

Config reference

Each servers entry is exactly the native @deepseek-ai/dsh-mcp-client config union.

stdio

FieldRequiredDefaultNotes
transportyes—stdio
serverNameyes—[A-Za-z0-9_-]{1,32}, unique per source list
commandyes—executable to spawn
argsno[]passed without shell interpolation
envno{}merged over the scrubbed ambient env
cwdno''child working directory
toolCallTimeoutMsno60000per-tool-call timeout
failOnStartupErrornofalsereject plugin activation on initial connection failure
reconnectnonative defaultsenabled, initialDelayMs, maxDelayMs, maxAttempts

streamable-http

FieldRequiredDefaultNotes
transportyes—streamable-http
serverNameyes—[A-Za-z0-9_-]{1,32}, unique per source list
urlyes—MCP endpoint URL
headersno{}extra request headers
toolCallTimeoutMsno60000per-tool-call timeout
failOnStartupErrornofalsereject plugin activation on initial connection failure
reconnectnonative defaultsenabled, initialDelayMs, maxDelayMs, maxAttempts

Develop

npm run typecheck
npm run build
npm test