Introduction¶

When extending agents in DeepSeek Harness (DSH), the common pain point is not just “can it call MCP,” but rather that MCP Server sources are scattered: different vendors’ endpoints, different authentication methods, and different stdio/HTTP execution modes often require manual configuration into mcpServers JSON. Once configured, you still have to handle OAuth login, API keys, tool and prompt discovery, connection disconnection, and restart recovery.

dsh-mcp-connector is a DSH plugin positioned as the DeepSeek Harness MCP connector and MCP Server market, designed for unified discovery, authorization, and connection management. DSH’s plugin ecosystem can be understood as “everything is a plugin”; the MCP Server market here is an independent community directory, not DeepSeek / Fantaworks’ official app store.

What is this¶

The repository is duhu2000/dsh-mcp-connector with an MIT license. The GitHub owner is duhu2000; the maintainer is QCC (企查查) as stated in the repository’s README/package.json.

The current public version is dsh-mcp-connector@0.2.32, corresponding to GitHub Release v0.2.32.

This plugin transforms MCP server integration from “one-time manual configuration” into a browsable, authorizable, manageable, and updatable market directory. It does not pretend to be a standalone DSH Skill; its capabilities mainly come from MCP tools and Prompts.

Core Features¶

Unified discovery, authorization, and connection management.
Supports OAuth 2.0 PKCE, API Key, stdio/HTTP, and mcpServers JSON import.
Supports tool and prompt discovery.
Provides a continuously updated curated connector directory, graphical market, graphical add, and connector details.
Prompt template support for variables like {{company}}, to be filled with the real query subject before sending.
Connection lifecycle management: connection persistence, restart recovery, start/stop, disconnect, OAuth auto-refresh/backoff recovery, and revocation.
Independent remote Registry; automatic fallback to built-in directory when the remote is unavailable.
Plugin version detection and security updates.
Smooth migration: explicitly scan and copy authorization from two old QCC OAuth plugins.
Conversation tools include:

mcp_connector_catalog、connect、configure、import_json、install_from_url、status、health_check、set_enabled、disconnect、refresh_catalog、publish、tools_list

Installation and Enablement¶

Requirements: DeepSeek Harness Desktop/web profile, Node.js 20 or higher.

First, execute the installation command:

dsh plugin --profile web add dsh-mcp-connector

Repeating the installation command upgrades it. You can also use the install script:

bash <(curl -fsSL https://raw.githubusercontent.com/duhu2000/dsh-mcp-connector/main/install.sh)

After installing or upgrading, fully restart DeepSeek Harness Desktop or dsh web. If using dsh web, you need to stop the original process first before starting; EADDRINUSE 127.0.0.1:3080 indicates an instance is already running.

After restarting, open the “MCP Connectors” entry on the left.

Typical Usage¶

Select a connector in the market and complete authorization or configuration.
Open the card details to view tools and Prompts.
If there is a sample Prompt in the details, you can click the send button to create/reuse a blank session in the current workspace and write the draft.
View, disable, restore, or disconnect connections in “Installed” or conversation tools.

After a successful connection, tools are provided to the model with the following prefix:

mcp__<serverName>__*

If you want to import existing configuration, you can use mcpServers JSON import; if you want to install via URL, you can use install_from_url or the graphical add entry.

Catalog and Configuration¶

The independent remote Registry can be updated separately, and market cards are visible after the client refreshes. As of 2026-09-01, the public Registry has published 97 connector descriptions; after merging and deduplicating with the 4 QCC cards included with the package, 101 cards can be browsed on the market page. The recommended slots strictly retain 4 QCC cards, PKULAW, and Wind, for a total of 6; other connectors are displayed by business category.

Bundle default configuration is located in cordis.patch.yml:

- id: mcp-connector
  name: dsh-mcp-connector
  config:
    catalogUrl: 'https://cdn.jsdelivr.net/gh/duhu2000/dsh-mcp-connector-registry@main/catalog.json'
    persistSecrets: true
    entryPrefix: mcp
    refreshSkewMs: 300000
    openBrowser: true

catalogUrl defaults to reading the public registry via jsDelivr CDN. Due to potential caching delays in jsDelivr’s branch URLs, new cards after registry merging are not guaranteed to appear instantly. If you need offline/private mode, you can explicitly set catalogUrl to an empty string.

Applicable Scenarios and Notes¶

Suitable for developers who are already using MCP in DSH Desktop/web and wish to reduce manual configuration and view connection status uniformly.

The plugin runs with the permissions of the current dsh / DeepSeek Harness process, so you should check the source code, publishing source, and MIT license before installing. When connecting to external MCP Servers, authorization information will be used for actual calls; before using API Key, OAuth, or stdio commands, ensure the corresponding service and command are trusted.

Regarding version releases, the Release is published via npm Trusted Publishing (GitHub OIDC), not relying on a long-term NPM_TOKEN.

Conclusion¶

The value of dsh-mcp-connector lies in putting MCP Server discovery, authorization, connection management, and Prompt tool discovery into the same DSH plugin. After installing or upgrading, enter from the left “MCP Connectors”; the GitHub repository address is:

https://github.com/duhu2000/dsh-mcp-connector

dsh-mcp-connector: MCP Connector and Server Market for DeepSeek Harness