dsh-mcp-connector plugin
A DeepSeek Harness plugin with a catalog of 100+ MCP connectors: OAuth or key sign-in, tool search and connection troubleshooting
- 125 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The plugin stores API keys and OAuth tokens for many external data services.
- Connections can give the agent access to corporate and paid provider data.
- Community connections were not released by the data providers themselves.
Install
Manual install
dsh plugin --profile web add dsh-mcp-connectorThe command from the getting-started section of the README; then a full restart of DeepSeek Harness.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The plugin stores API keys and OAuth tokens for many external data services.
- Connections can give the agent access to corporate and paid provider data.
- Community connections were not released by the data providers themselves.
This is third-party code. Review the repository files before installing.
What it does
dsh-mcp-connector adds an MCP connectors section to DeepSeek Harness: a catalog of 100+ connections to vertical data sources and open services such as company registries, statistics and scientific papers. You can connect through OAuth 2.0 PKCE, an API key, Streamable HTTP, stdio or an import of `mcpServers` JSON. The tools page searches across all enabled connections of the current scope and shows types and required parameters, the source and the time of the last successful cache. On failure you can check the connection or discover the tools again. The visibility scope, project or global, and rules on three levels, connection, server and tool, are set separately. For selected connections schemas stay hidden by default and the agent enables only the needed tools for the session.
Who it is for. DeepSeek Harness users who connect external MCP data servers from one window without hand-editing configs.
Good fit when
- An agent needs company, patent or scientific paper data from a ready connector catalog.
- An existing `mcpServers` JSON is moved into DSH and the connections should be checked in one place.
- OAuth sign-in fails and you need diagnostics by stage and error code.
- A tool has to be found by name or description among all enabled connections.
Not a fit when
- Your main environment is Claude Code or Cursor: the plugin targets DeepSeek Harness.
- You need the official server of the data provider itself: community connectors are not official.
- You want to run target tools from the plugin page: it searches and diagnoses but does not execute them.
Example request
Find the tool for company lookups among the enabled connections and show its required parameters.Limitations
After installing or upgrading, DeepSeek Harness Desktop or the `dsh web` process has to be fully restarted; a page refresh is not enough. OAuth sign-in depends on client registration, account rights and provider policy. A saved connection, discovered tools and a successful call are verified separately: each step can fail on its own. Provider accounts, quotas and fees are outside the plugin. The native sidebar entry works on DSH 0.2.0-rc.2 and newer, and 0.1.x gets a compatible fallback entry.
How to disable. Remove the plugin from the DSH profile through the plugin manager and restart DeepSeek Harness. Saved connections and credentials are stored locally, so delete them in the plugin before uninstalling.
FAQ
How do I install dsh-mcp-connector?
Run `dsh plugin --profile web add dsh-mcp-connector` or find the package by its full name in the plugin market. Then fully restart DeepSeek Harness Desktop or `dsh web`.
Which connection methods are supported?
OAuth 2.0 PKCE, an API key, Streamable HTTP and stdio, plus an import of `mcpServers` JSON. Manual adding offers an HTTP or stdio form and entry by a connector description.
Where are credentials stored?
Locally on your machine. The plugin refreshes authorization, makes backups without secrets and keeps the previous connection on failure.
Are these the official servers of the data providers?
Not always. Community connections do not mean the provider itself released the server. Rights, quotas and calls need checking per service.
What does the tools page do?
It searches tools by name and description across enabled connections, shows parameters, source and cache time and helps on failures: check the connection or discover the tools again.
Discussion
No questions or reviews yet.
Related
PluginsA DeepSeek Harness plugin-runner: starts and stops the rlm-tools-bsl MCP server for 1C code analysis alongside DSH and registers it in the MCP manager itself
MCP plugin for DeepSeek Harness to drive a Windows desktop: reads controls, clicks, types, takes screenshots, runs OCR.
Zapier's official MCP plugin: the agent gets actions across thousands of apps through your Zapier account
An MCP server for Home Assistant: the agent reads smart-home state and controls devices through your instance
An MCP server for remote Windows control: screenshots, PowerShell, files, mouse and keyboard, registry and OCR
A free WordPress plugin with an MCP server of 200+ tools: Claude, ChatGPT and Cursor manage your site, WooCommerce and menus
README in short
The plugin calls itself a data marketplace for DeepSeek Harness: data providers and open sources sit on one panel with shared authorization. By skill extension it means MCP tools and prompts and does not pose as a separate DSH skill.