DeepSHPlugins
dsh-oomol 專案預覽
GITHUB / COMMUNITY PROJECT

dsh-oomol

工具與整合TypeScriptMIT

將 DeepSeek Harness 接入由 OOMOL 管理的應用與服務,支援漸進式發現並執行 Connector Actions,並提供用於管理 Provider 連線的應用內面板。

13 Starsoomol-lab 更新時間 2026-08-20
訪問 GitHub 倉庫
dsh-oomol 專案預覽

專案介紹

中文

將 DeepSeek Harness 接入由 OOMOL 管理的應用與服務,支援漸進式發現並執行 Connector Actions,並提供用於管理 Provider 連線的應用內面板。

English

Connects DeepSeek Harness to OOMOL-managed apps and services, with progressive Connector Action discovery and execution plus an in-app panel for managing Provider connections.

專案資訊與收錄訊號

快照 2026-09-11
作者 / 組織
oomol-lab
倉庫
oomol-lab/dsh-oomol
GitHub Stars
13
Forks
1
開發語言
TypeScript
許可證
MIT
最近推送
2026-08-20
Manifest
資料中檢測到宣告

公開倉庫不自動等於可商用;許可證與當前相容性以原專案文件為準。Manifest 和資料評分不構成安裝安全認證。

資料評分

72/ 100
維護活躍
85
文件與實用資訊
85
生態關注度
35
安裝便捷訊號
80
專案宣告訊號
100

近 22 天仍在更新;README 含完整安裝與使用說明。

評分來自已有資料快照的五維模型,僅作瀏覽參考,不是實際使用評測或安全檢測結論。

安裝與使用

所有專案資料與許可均以對應 GitHub 倉庫為準。

dsh plugin --profile web add dsh-oomol

複製命令不會自動執行。請先閱讀倉庫文件,確認環境要求與許可證。

專案截圖

倉庫 README

GitHub 原文

已儲存的倉庫文件快照;文件抓取時間未記錄,可能與上方目錄介紹處於不同版本。安裝前請核對當前倉庫說明。

儲存庫檔案保留原文,指令與授權文字不作自動改寫。

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.

npm package | 中文文档

Requirements

  • Node.js 22.19 or later within Node.js 22, or Node.js 24+
  • DeepSeek Harness 0.1.0-rc.7 or 0.1.0-rc.8
  • 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 under Settings > Plugins > OOMOL Connector.

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 in the plugin settings. 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 in the plugin settings. 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

FieldDefaultPurpose
endpointhttps://connector.oomol.com/v1/mcpStreamable HTTP MCP endpoint
apiKeyEnvDerived from endpointHarness credential reference and launch environment name
teamNameunsetOOMOL Hosted team identity
teamNameEnvOOMOL_TEAM_NAMEOOMOL Hosted team environment name
serverNameoomolHarness MCP tool namespace
toolCallTimeoutMs60000Tool call timeout
failOnStartupErrorfalseFail Harness startup when MCP discovery fails

Derived credential references:

Endpoint modeDefault referenceRequired
OOMOL HostedOOMOL_MCP_API_KEYYes
Self-hostedOOMOL_CONNECT_RUNTIME_TOKENDepends on the OpenConnector deployment

Troubleshooting

SymptomAction
Plugin missing from SettingsInstall it in the web profile and restart dsh web
OOMOL Hosted shows Not configuredSave an OOMOL MCP API key in plugin settings
Self-hosted returns UnauthorizedSave a runtime API key created by that OpenConnector instance
Self-hosted Console link returns 404Open the Console URL configured by the OpenConnector deployment
Expected app is missingOpen the relevant Connector Console and configure the Provider connection
Connections panel stays closedWiden the window to at least 1220 px so Harness can show its details column

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

使用前核對

安裝步驟、相容版本與授權範圍以原專案當前文件為準。Stars 和評分是快照中的導航訊號。

安裝與排錯 · 專案問題反饋

同類專案