OOMOL Connector for DeepSeek Harness
Use OOMOL Connector Actions from DeepSeek Harness through progressive MCP discovery.
dsh-oomol supports OOMOL Hosted and self-hosted OpenConnector. One plugin instance connects to one Connector endpoint.
Requirements
- Node.js 22.19 or later within Node.js 22, or Node.js 24+
- DeepSeek Harness
0.2.0-rc.2through 0.2.1 (0.2.1 starts at0.2.1-rc.1, its alphas are not supported) - An OOMOL account for OOMOL Hosted, or a running OpenConnector instance for self-hosted use
Install
Install the plugin into the Web profile and restart Harness:
dsh plugin --profile web add -w dsh-oomol
dsh web
The plugin appears on the Plugins page as dsh-oomol. Open it to configure the Connector key.
OOMOL Hosted
The package connects to OOMOL Hosted by default:
- id: oomol
name: dsh-oomol
config:
endpoint: https://connector.oomol.com/v1/mcp
teamNameEnv: OOMOL_TEAM_NAME
serverName: oomol
toolCallTimeoutMs: 60000
failOnStartupError: false
Create an OOMOL MCP API key in OOMOL Console, then save it on the plugin page. Harness Credentials stores the key under OOMOL_MCP_API_KEY.
Managed environments can provide it at launch:
export OOMOL_MCP_API_KEY="api_..."
dsh web
Set a team identity when needed:
export OOMOL_TEAM_NAME="your-team"
dsh web
The Connections button opens the native Harness panel for OOMOL Hosted accounts.
Self-hosted OpenConnector
Override the endpoint in the profile's cordis.patch.yml:
- update:
id: oomol
config:
endpoint: http://127.0.0.1:3000/mcp
The plugin recognizes every non-official endpoint as self-hosted. Local OpenConnector deployments can run without authentication. Deployments with runtime authentication use the key stored under OOMOL_CONNECT_RUNTIME_TOKEN:
export OOMOL_CONNECT_RUNTIME_TOKEN="oct_..."
dsh web
You can also save the runtime API key on the plugin page. Create persistent runtime keys in the OpenConnector Console Access page.
Self-hosted HTTP endpoints are limited to localhost, 127.0.0.1, and [::1]. Remote deployments use HTTPS:
- update:
id: oomol
config:
endpoint: https://connect.example.com/mcp
The Connections button opens the endpoint origin, such as https://connect.example.com, where OpenConnector serves its Console.
Custom API key environment name
Both modes support an explicit credential reference:
- update:
id: oomol
config:
endpoint: https://connect.example.com/mcp
apiKeyEnv: MY_CONNECT_RUNTIME_TOKEN
Harness Credentials resolves apiKeyEnv first and the launch environment second.
Use Connector Actions
Start with discovery:
Show me the connectors available to this account.
Find Actions that can create a calendar event and inspect the selected Action schema.
For operations with external effects, include the target account and proposed arguments in your request before execution.
How it works
The plugin mounts DeepSeek Harness's Streamable HTTP MCP client with the selected Connector endpoint. Connector Actions remain progressively discoverable, keeping the permanent Harness tool surface small.
OOMOL Hosted stores Provider credentials in OOMOL Connector. Self-hosted deployments store them in OpenConnector. Harness stores only the Connector client key selected by apiKeyEnv.
The browser receives the credential reference and status metadata. Connector API keys and Provider credentials stay in Host-side secret boundaries.
See Architecture for implementation details.
Configuration
Derived credential references:
Troubleshooting
Run local diagnostics:
pnpm run doctor
Security
- Store Connector API keys in Harness Credentials or the launch environment.
- Use HTTPS for remote self-hosted endpoints.
- Review destructive, externally visible, permission-changing, and broad-sharing Actions before execution.
- Treat an ambiguous side-effecting call as an unknown outcome and inspect the Provider before retrying.
- Report vulnerabilities through SECURITY.md.
Development
pnpm install --frozen-lockfile
pnpm check
Build and install the checkout into a Web profile:
pnpm build
dsh plugin --profile web add -w "$(pwd)"
License: MIT