dsh-mcp-oauth-client

Connecting multiple MCP services in DeepSeek Harness often means juggling different authentication flows, transport protocols, and local process configurations—manually editing YAML files is error-prone and lacks visibility. dsh-mcp-oauth-client tackles exactly this: it provides a unified visual panel inside DSH where you can add, disable, reconnect, and inspect every service at a glance, without constantly editing configuration files.

The plugin covers two primary transport types. For Streamable HTTP services it supports four authentication modes: no auth, OAuth 2.1 with PKCE, Bearer token, and custom headers. For local stdio services you can configure the executable command, arguments, environment variables, and working directory. The OAuth flow automatically opens your browser and completes authorization via a local callback, while token refresh is handled by the official MCP SDK. Added services persist to the current profile's cordis.patch.yml; OAuth access and refresh tokens stay in process memory only and are never written to disk by the plugin.

It is best suited for DSH developers who need to integrate several MCP toolchains with heterogeneous authentication requirements. The plugin acts purely as a management bridge—it ships no default service endpoints or credentials, and every configuration is defined by you through the interface, keeping the deployment as minimal as possible.