MicroHEROX/dsh-exa-mcp

Name: MicroHEROX/dsh-exa-mcp
Author: MicroHEROX

Plugin插件 Native原生 ⭐ 3 MIT Notifications & Remote通知与远程

Exa Search MCP for DeepSeek Harness：通过内置的 @deepseek-ai/dsh-mcp-client 桥接器挂载远程 Exa MCP 端点（https://mcp.exa.ai/mcp）

Project Overview项目介绍

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

This is a native DSH plugin that connects Exa’s neural web search engine to DeepSeek Harness via the Model Context Protocol. It uses the official MCP client bridge built into the DSH CLI to connect to Exa’s hosted MCP endpoint, and registers four Exa tools as native DSH agent tools under the exa namespace. The plugin is a pure configuration bundle with no local code to build or execute, and it never modifies your core DSH installation, only adding a single entry to your cordis configuration file. To install the recommended bundled version, first make sure you have pnpm installed globally, then run dsh plugin --profile web add github:MicroHEROX/dsh-exa-mcp and start DSH with dsh web.

After installation, you can optionally set an Exa API key as an environment variable to unlock advanced features like Exa Agent and lifted rate limits. If you do not set an API key, the plugin falls back to anonymous free tier usage, which works for basic web search and fetch tasks. To verify the plugin works correctly after installation, wait for initial asynchronous tool discovery, then ask DSH to use Exa to search for and summarize recent DeepSeek Harness release notes. If the tools are called successfully, the plugin is active and ready. This plugin is ideal for DSH users who want high-quality neural web search in their agent workflows.

This plugin is released under the open source MIT license, and requires DSH CLI version 0.1.0-rc.5 or newer to work correctly. It is compatible with all major desktop platforms including Windows, macOS, and Linux, and recommends Node.js 22 or higher for best results. The plugin never stores your API key locally, only reads it from your environment at load time and sends it directly to Exa, so no sensitive data is written to any configuration file. Uninstalling the plugin is simple: just remove the configuration entry from your cordis patch file, no changes to core DSH files are needed. Exa’s hosted endpoint is maintained by Exa, and free usage is subject to their rate limits.

这是一个专为DeepSeek Harness（DSH）打造的原生第三方插件，它将Exa神经网页搜索与抓取引擎通过MCP协议接入DSH，借助DSH CLI内置的MCP客户端桥接连接Exa官方托管的MCP端点，在exa命名空间下注册四款原生代理工具。它本身仅提供配置包，无需本地构建，不会修改DSH核心安装文件，仅需在配置文件中添加对应配置即可完成集成，对原有DSH环境无侵入。

用户安装完成后，只需设置环境变量EXA_API_KEY即可解锁全部高级功能，不设置也可使用Exa免费 tier的速率限制基础功能，满足一般搜索需求。安装方式灵活，支持插件包安装、一次性补丁覆盖、手动合并配置三种方式，卸载仅需删除对应配置行，不影响原有DSH环境。适合需要使用Exa高精度网页搜索能力增强DSH代理功能的开发人员使用。

本插件遵循MIT许可协议，要求DSH CLI版本不低于0.1.0-rc.5，推荐使用Node.js 22及以上版本，兼容Windows、macOS、Linux全平台。插件本身不会存储或写入EXA_API_KEY，仅在加载时从环境变量读取后发送给Exa，安全可控。Exa官方端点由Exa官方维护，免费匿名使用存在速率限制，配置API密钥可解除限制并解锁高级功能。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-exa-mcp（MicroHEROX/dsh-exa-mcp）
仓库：https://github.com/MicroHEROX/dsh-exa-mcp
本站详情页：https://www.yhbd.top/plugins/microherox-dsh-exa-mcp/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 3 · 最近提交 2026-08-21

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

【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 warning1 项注意

Only 3 stars - very few users, little community feedback星标只有 3，几乎没人在用，遇到问题缺少社区反馈

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 github:MicroHEROX/dsh-exa-mcp

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

READMEREADME

10.6 KB · 缓存于 2026-08-23 03:42:19 · 10.6 KB

Exa Search MCP for DeepSeek Harness

English · 中文

A third-party plugin that brings Exa — the neural web search and fetch engine — into DeepSeek Harness (dsh). It connects to Exa's hosted MCP endpoint (Streamable HTTP) through the MCP client bridge that ships with the dsh CLI, and registers Exa's tools as native agent tools under the exa namespace.

mcp__exa__web_search_exa   ·  mcp__exa__web_fetch_exa
mcp__exa__web_search_advanced_exa  ·  mcp__exa__agent_run   (with an API key)

Zero install footprint: no code runs in the dsh process — the upstream is Exa's official hosted endpoint.
Pure configuration bundle: one patch layer, no build step, no runtime API.
Never touches your deepseek-harness installation; it only adds one row to the composed cordis.yml.

Quick Start

1. Install

Option A — install as a plugin bundle (recommended, requires pnpm):

npm install -g pnpm
dsh plugin --profile web add github:MicroHEROX/dsh-exa-mcp
dsh web

Verify after a github: install — when the route to github.com is unstable, a github: (git) install can silently fail or finish with an un-synced dsh.profile.bundles (local link:/file: installs are unaffected). Verify and fix in one step:
# check: does the bundle layer appear?
dsh --profile web --dump-config | grep -A2 "== dsh-exa-mcp"
# if not (or to fix preemptively), append the bundle to the profile manifest:
node -e "const fs=require('fs');const p=process.env.DSH_HOME+'/profiles/web/package.json';const j=JSON.parse(fs.readFileSync(p,'utf8'));if(!(j.dsh.profile.bundles||[]).includes('dsh-exa-mcp')){j.dsh.profile.bundles=[...(j.dsh.profile.bundles||[]),'dsh-exa-mcp'];fs.writeFileSync(p,JSON.stringify(j,null,2)+'\n','utf8');console.log('fixed: dsh-exa-mcp appended');}else{console.log('already present');}"
The timing issue is reported upstream (Discussions #656); --patch overlays are never affected.

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

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