DSH Plugin HubDSH 插件市场
oomol-lab/dsh-oomol 预览 preview

oomol-lab/dsh-oomol

Plugin插件 Native原生 ⭐ 12 MIT Models & Routing模型与路由

OOMOL DeepSeek 连接器——通过渐进式 MCP 发现机制，发现已连接的应用并执行操作，同时不会暴露供应商凭据。

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

dsh-oomol is a native DeepSeek Harness plugin that enables DSH users to access OOMOL Connector actions via progressive Model Context Protocol (MCP) discovery. It supports both OOMOL Hosted and self-hosted OpenConnector endpoints, with one plugin instance connecting to exactly one endpoint. It is distributed via npm as a public package, and can also be built from source for local development. To install the plugin, users run the dsh CLI command dsh plugin --profile web add -w dsh-oomol, then restart the DSH web service via dsh web to activate it.

This plugin is designed for AI developers who want to use OOMOL Connector capabilities directly from their DeepSeek Harness workflow. To use the OOMOL Hosted service, users first create an MCP API key from the OOMOL Console, then save the key to DSH Credentials or inject it via the OOMOL_MCP_API_KEY environment variable at DSH launch. To start using connector actions, users send a natural language prompt to DSH asking to discover available connectors or specific actions for their task. DSH will progressively discover actions through MCP, so the core tool list stays small and uncluttered.

The plugin is released under the open source MIT license, and requires Node.js 22.19 or later (or Node.js 24+) and DeepSeek Harness version 0.1.0-rc7 or rc8 to run. For self-hosted OpenConnector, users can override the default endpoint in the cordis.patch.yml configuration file, and only localhost endpoints and HTTPS remote endpoints are allowed. All API keys and provider credentials are stored on the host side within secret boundaries, so sensitive data never gets exposed to the DSH browser client. Users can run a local diagnostic command pnpm run doctor to troubleshoot common issues.

dsh-oomol 是专为 DeepSeek Harness 开发的原生插件，用于通过渐进式模型上下文协议（MCP）发现，调用 OOMOL Connector 提供的各类操作。它同时支持 OOMOL 官方托管服务和用户自建部署的 OpenConnector 实例，一个插件实例仅连接一个 Connector 端点。用户可通过 dsh 命令行工具将其安装到 DSH 的 Web 配置文件中，安装后重启 DSH Web 服务即可在设置面板中找到该插件。

该插件面向需要在 DeepSeek Harness 中调用 OOMOL Connector 能力的 AI 开发人员。使用前需要在 OOMOL 控制台创建 MCP API 密钥，将其保存在 DSH 凭据管理中，也可以在启动 DSH 时通过环境变量注入密钥和团队标识。用户可通过自然语言指令让 DSH 发现可用连接器和对应操作，查看操作的参数结构后再执行目标调用。

该插件采用 MIT 许可证开源，使用时需要满足环境依赖：Node.js 22.19 及以上版本，或 Node.js 24 及以上，同时要求 DeepSeek Harness 版本为 0.1.0-rc7 或 rc8。自建部署的 OpenConnector 仅允许本地回环地址或 HTTPS 远程端点，密钥和凭据都存储在主机侧，不会泄露给浏览器端。

View on GitHub在 GitHub 查看

Recommended强烈推荐 Send to your DSH发给你的 DSH 安装 
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-oomol（oomol-lab/dsh-oomol）
仓库：https://github.com/oomol-lab/dsh-oomol
本站详情页：https://www.yhbd.top/plugins/oomol-lab-dsh-oomol/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 12 · 最近提交 2026-10-01 · 主语言 TypeScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 note1 项提示
  • 12 stars - an early-stage project星标 12，属于早期项目
DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

  • DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
  • External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
  • Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

  • Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
  • Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
  • curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
  • Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
  • Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
  • Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装 

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

把 oomol-lab/dsh-oomol 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

5.8 KB · 缓存于 2026-10-01 22:10:20 · 5.8 KB

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.2.0-rc.2 or later within 0.2.0
  • 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:

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 oomol-lab/dsh-oomol 的 README.md。 在 GitHub 查看原文 →

Related相关推荐

← 上一个 Prev holdem 下一个 Next dsh-codegraph →