dsh-mcp-servers

1. 安装并启动 DeepSeek Harness：npx @deepseek-ai/dsh web
2. 在终端执行上面的安装命令（CLI 会解析插件并核验来源）
3. 用 dsh plugins list 确认已安装，必要时重启 Harness 生效

插件以当前 dsh 进程的权限运行，安装时可能执行代码。请先通读仓库源码与许可证，确认无破坏性命令与越权访问；本站只做索引，不对第三方插件安全性作担保。

事实信息来自公开插件目录快照（2026-10-01），介绍文案由本站再加工。

以下为插件仓库 README 全文（原始内容，由公开目录抓取整理）。

# dsh-mcp-servers

Expose [Model Context Protocol](https://modelcontextprotocol.io) servers as tools inside [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness). A dsh **bundle** with both a server half (connects to MCP servers, registers their tools) and a client half (a settings UI in the web app).

Made with DeepSeek V4 Flash.

## Features

- **stdio, streamable http, and legacy SSE** transports — one shared endpoint field, tabs in the UI
- **Tools registered automatically** under `mcp____` — the same server-qualified shape the official `@deepseek-ai/dsh-mcp-client` and Claude Code use (e.g. server id `shadcn` → `mcp__shadcn__get_component`); names are normalized to `[A-Za-z0-9_-]`, capped at 64 chars, and get a deterministic 12-hex hash suffix when normalization/truncation would collide
- **`tools/list_changed` re-sync** — when a server signals its tool list changed, the generation re-registers in place (old tools stay live until the new set registers)
- **Live status dots** — green when connected, red with the reason on failure; auto-reconnects with backoff when a connection drops (idle SSE streams, crashed processes)
- **Test button** per card — probes connect + tool listing against the current draft without registering anything
- **Edit cards** — type tabs, command/args textarea, env variables (or http headers) as key/value rows with show/hide values, paste `.env` from the clipboard, enabled switch
- **Tabs**: All / Local / Remote / Backup & Restore
- **Backup & Restore**: export/import the server list as JSON (with inline preview), and optional **WebDAV sync** (push/pull, https-only, Basic auth) plus an optional **daily automatic backup at 12:00 PM** — password stored server-side as a secret, never sent back to the browser

## Install

Requires DeepSeek Harness with the `dsh` CLI.

```sh
# from a directory containing this repo (or publish it, then use the bare name);
#  is the profile you boot, e.g. `web`
dsh plugin --profile  add ./dsh-mcp-servers
dsh --profile
```

Then open Settings → **MCP Servers**, add a server, hit **Test**, and **Save**.

### Other install methods

From a built tarball (`npm run pack` produces `dsh-mcp-servers-.tgz`):

```sh
dsh plugin --profile  add ./dsh-mcp-servers-.tgz
```

Rebuild after changes with `npm run build` — profiles load the built `dist/` and `client/client.js`, not the sources.

## Configuration

### stdio server

| field | example |
| --- | --- |
| type | `stdio` |
| command | `npx` |
| command args | `-y`
`@modelcontextprotocol/server-everything` (one per line, first line is the command) |
| env | key/value rows, e.g. `API_KEY` / your token |

### http / sse server

| field | example |
| --- | --- |
| type | `http` (streamable) or `sse` (legacy event-stream) |
| url | `https://example.com/mcp` or `https://example.com/sse` |
| headers | key/value rows (e.g. `Authorization` / `Bearer …`) |

### Backup & Restore

- **Local file**: export the current config (all servers, endpoints, env, headers) as JSON, import it back, or preview what would be exported.
- **WebDAV**: URL, username, password (https only), Push/Pull. Toggle **Back up daily at 12:00 PM** to auto-push every day at noon local time.

## Development

```sh
npm install          # note: .npmrc sets legacy-peer-deps (two framework rc lines)
npm run build        # server dist/ + client bundle
npm run check        # typecheck (server + client) + sanitizer test
npm run pack         # build + produce dsh-mcp-servers-.tgz
npm run publish:npm  # build + publish to npm (run `npm login` first)
```

Versioning is build-based: `1..` (e.g. `1.260817.1`); the counter increments on every build and resets each day.

The client UI follows the Harness design system: primitives are host-injected externals (`@deepseek-ai/dsh-client-ui-primitives`) and native controls use `--dsw-*` theme tokens with hex fallbacks.

## Notes / limitations

- Tool input schemas are whitelist-stripped to the Harness-supported JSON Schema subset (`src/sanitize.ts`); unsupported keywords (`minLength`, `format`, `anyOf`, schema-form `additionalProperties`) are dropped.
- MCP results render as text; image/resource blocks collapse to JSON/text, not rich blocks.
- WebDAV requires an https endpoint; credentials in the URL are rejected (passed separately).
- Config/WebDAV routes are loopback-only.