oomol-lab/dsh-oomol

Connects DSH to OOMOL Connector Actions over progressive MCP discovery, against hosted or self-hosted OpenConnector.

The OOMOL Connector for DeepSeek Harness exposes OOMOL Connector Actions as DSH tools through progressive MCP discovery, so the agent learns about tools as it needs them instead of loading an entire catalog into context up front. It supports both OOMOL Hosted, pointed at the hosted connector endpoint by default, and a self-hosted OpenConnector instance. Configuration lives on the plugin page in the DSH UI, where you save an MCP API key created in the OOMOL Console; Harness Credentials stores it under OOMOL_MCP_API_KEY. Documented settings include the endpoint, a team-name environment variable, a server name, and a tool-call timeout that defaults to 60 seconds. The Connections button opens the native Harness panel for OOMOL Hosted accounts.

Notifications & Integrations ★ 11
View on GitHub ↗

Install

dsh plugin --profile web add -w dsh-oomol

The README's install block, verbatim, including the -w flag, followed by dsh web to restart. One plugin instance connects to one Connector endpoint, so multiple endpoints mean multiple configured instances. After install the plugin appears on the Plugins page as dsh-oomol, and you save the Connector key there rather than in a config file.

Compatibility

Requires Node.js 22.19 or later within Node.js 22, or Node.js 24+. Requires DeepSeek Harness 0.2.0-rc.2 through 0.2.1, and the README is precise that 0.2.1 support starts at 0.2.1-rc.1 and that its alphas are not supported. An OOMOL account is needed for OOMOL Hosted, or a running OpenConnector instance for self-hosted use.

Details

Alternatives

aokamoaki/dsh-notify · good-boy4069/dsh-mobile-remote · xmanrui/dsh-im

More plugins in Notifications & Integrations

Browse more in Notifications & Integrations

Guides for Notifications & Integrations plugins