DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
P

dsh-plugin-baizhi-agent-toolkit

Plugin Baizhi Agent Toolkit

适用于 DeepSeek Harness 的可选 BaizhiCloud Agent Toolkit MCP 配置包

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:ct-jaryn/dsh-plugin-baizhi-agent-toolkit#24a5514c4f394755389e0e45304f404ada2fa072
README兼容性版本

兼容性与来源证明

Plugin Baizhi Agent Toolkit 以 dsh-plugin-baizhi-agent-toolkit 发布,当前版本为 0.1.0。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/9/21

版本

0.1.0stable
2026/9/21

相关插件

正在加载相关插件…

最新版
0.1.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/9/21
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 integrations-communication 分类下经过校验的插件。

Acp App@deepseek-ai/dsh-acp-appdsh ACP 配置文件包:基于 dsh-base 的仅限自动化的 JSON-RPC stdio 和进程生命周期管理Ds Botds-botDS Bot:DeepSeek Harness 的一组长期运行的 Bot,支持主 Bot、Bot 间消息和群聊Remote Bridge@linxin666/dsh-remote-bridgeDSH 远程桥接:主机端通过唯一且精确的 /ios/v1 WebSocket 路由提供协议 v1——会话列表、历史记录基线、提示、包含工具活动的实时回合增量、中断以及进程内代理审批——连接到通过一次性配对的设备Free Searchdsh-free-searchDeepSeek Harness 的免费网页搜索:42 个引擎(Bing/DuckDuckGo/AnySearch/SearXNG/Exa/Tavily/Keenable/Firecrawl/Parallel/Brave/Zhipu/You.com 无需密钥;Zhihu 通过 MCP 支持全局/站内搜索,以及 Perplexity/SerpBase/DeepSeek(官方 + 原生工具/搜索)/Baidu/Kimi/

README

BaizhiCloud Agent Toolkit for DeepSeek Harness

An optional community configuration bundle for the hosted BaizhiCloud Agent Toolkit. It loads DSH's existing MCP client with the service's Streamable HTTP endpoint and an API-key bearer header. It adds no transport, backend implementation, credential store, or default model provider.

This contribution is part of integration and promotion work for BaizhiCloud Agent Toolkit; it is not an official DeepSeek integration.

Requirements

  • DeepSeek Harness 0.1.5-rc.2 and pnpm on PATH. The MCP peer dependency is pinned to the tested release; compatibility with 0.1.6 alpha or later versions has not been established.
  • Your own BaizhiCloud Agent Toolkit account and API key, available as BAIZHI_API_KEY in the DSH process environment. Review service pricing before calling tools. Keep the key out of Git, patches, and shared logs.
  • An existing DSH profile with the standard tools runtime and network access to https://agent-toolkit.app.baizhi.cloud/mcp.

Install in your chosen profile

From a reviewed checkout of this bundle:

npm pack --ignore-scripts
npx @deepseek-ai/dsh@0.1.5-rc.2 plugin --profile web add /absolute/path/to/dsh-plugin-baizhi-agent-toolkit-0.1.0.tgz --ignore-scripts

Replace web with the profile you actually use. DSH installs the package in that profile and adds its declared bundle to the profile's layer list. There is no build or install hook. Package installation alone does not authenticate the hosted service.

Provide BAIZHI_API_KEY using your normal environment/secret mechanism, then restart the selected profile. Missing, empty, or whitespace-only values disable this bundle entry, so it makes no connection until a nonempty key is available. A supplied value is trimmed before use in Authorization: Bearer ….

The MCP client discovers the service's current tool catalog dynamically. DSH namespaces tools as mcp__baizhi__<remote-tool-name>. Review the actual offered tools and requested operation before approving calls; this bundle does not restrict the service to search/read or promise that every exposed tool is read-only.

A first task after connecting: Find the official Model Context Protocol transport documentation, read the relevant page, and summarize it with source links. Success means the tool returned useful content and the linked sources support the summary. A visible configuration entry, local test, or discovered catalog alone is not production acceptance.

Data, failures, and removal

Tool inputs, including search queries, URLs, and any other approved arguments, are sent to BaizhiCloud. Calls may incur charges. This is static API-key bearer authentication, not OAuth. Service access and tool availability depend on your account.

If tools are absent, check whether the selected profile loaded this bundle and whether its process has a nonempty key. Connection/authentication failures do not intentionally stop the rest of the profile (failOnStartupError: false); the existing MCP client's reconnect behavior still applies. A 401 requires correcting account/key access, not installing another login wrapper.

To remove it from a profile:

npx @deepseek-ai/dsh@0.1.5-rc.2 plugin --profile web remove dsh-plugin-baizhi-agent-toolkit

Restart the profile afterwards. Removing a local bundle does not revoke a remote API key; manage keys in your BaizhiCloud account.

Validation and scope

npm ci --ignore-scripts
npm test

Six tests use the actual published DSH profile/bundle loader, Cordis lifecycle, tools registry, and MCP client against a loopback HTTP fixture with synthetic credentials. They cover initialize, tool discovery, registry dispatch, bearer rejection, missing/empty/whitespace credentials, and disposal. The test runner isolates HOME and environment; it overrides only the endpoint and reconnect policy inside the test profile and never calls the production endpoint. Disposal checks stream closure, tool unregistration, and no reconnect; it does not claim server-side session deletion.

The tests do not exercise a live BaizhiCloud account, model, web UI, production billing, every operating system, or newer DSH releases. The public integration project and this MIT configuration bundle do not make the hosted backend open source. This is an independent community integration, not an official DeepSeek endorsement.