dsh-oomol

Many DeepSeek Harness users want external connectors, automation services, or internal APIs to appear inside the same conversational workflow. The problem is not simply adding more tools, but adding them in a way that keeps the tool surface small, predictable, and safe. dsh-oomol addresses this by connecting OOMOL Connector to DeepSeek Harness through progressive MCP discovery, allowing the assistant to find and invoke Connector Actions when needed instead of presenting a crowded catalog of tools.

The plugin’s core value is its discovery model. It mounts Harness’s Streamable HTTP MCP client against a selected Connector endpoint, then exposes OOMOL or OpenConnector actions progressively. That means users can work with a focused assistant while still reaching a broader set of operations behind the scenes. For calls that create external effects, dsh-oomol encourages including the target account and proposed arguments before execution, making side-effecting actions easier to review. It supports both OOMOL Hosted and self-hosted OpenConnector deployments, with each plugin instance connecting to one endpoint and keeping credential boundaries clear between Harness and the connector side.

This plugin is best suited for individuals and teams already using DeepSeek Harness in a web profile who need to bring OOMOL Connector or self-hosted OpenConnector actions into their assistant workflows. It is especially useful when the goal is not to dump every API endpoint into the prompt, but to connect a governed set of tools that remain discoverable, auditable, and separated by environment. In short, dsh-oomol turns external connector actions into a safer, more progressive part of the Harness experience.