Introduction

The design philosophy of DeepSeek Harness (DSH) is “everything is a plugin.” An Agent invokes local capabilities such as file access and search through DSH. Model Context Protocol (MCP) is the current standard protocol for Agent tool invocation. The existing dsh-mcp-client addresses the question of “how to connect external MCP services into DSH,” while dsh-mcp-bridge addresses the reverse question: how to expose DSH capabilities to external MCP clients (such as Claude Code and Codex).

The following sections describe how to use this plugin.

What Is It

dsh-mcp-bridge is a plugin that converts the DeepSeek Harness toolset into a standard MCP server (via streaming HTTP). It allows any MCP-compatible client to access DSH tools through an HTTP endpoint.

  • Owner: liiiubai
  • Category: Network tools
  • License: MIT
  • Stars: 1

The plugin runs on top of DSH’s sandboxing and approval workflow, ensuring that external calls are securely validated.

Core Features

  1. Standard MCP server: Exposes DSH tools as MCP protocol services and supports streaming.
  2. Multi-client support: Can be driven by Claude Code, Codex, or any client/SDK that follows the MCP protocol.
  3. Security controls: Provides a secure allowlist mechanism, exposing only low-risk tools (read, glob, grep, web_search), and uses a hard denylist to prevent dangerous commands (such as write, edit, pwsh) from being misused.
  4. Zero dependencies: Implemented in pure JavaScript with no build step required.
  5. Native sandboxing: All tool calls still go through DSH sandbox isolation and approval workflows.

Installation and Enablement

The installation process is completed through DSH plugin commands.

  1. Run the install command:
    dsh plugin --profile <name> add github:you/dsh-mcp-bridge

*Note: Replace `<name>` with the name of the DSH configuration profile you are actually using.*
  1. The plugin automatically mounts a cordis.patch.yml configuration file and maps the server endpoint to /mcp.

Typical Usage

After installation, configure the allowlist and connect the client.

  1. Edit your cordis.patch.yml, and adjust the endpoint path and allowed tools:
    - id: mcp-bridge
      config:
        path: /mcp                        # 端点路径
        allowlist:                        # 暴露给 MCP 客户端的 DSH 工具
          - read
          - glob
          - grep
          - web_search
  1. Connect Claude Code or another MCP client:
    claude mcp add --transport http dsh http://127.0.0.1:3080/mcp

The client will recognize tools prefixed with `dsh_` (for example, `dsh_read`, `dsh_glob`).

Use Cases and Notes

  • Use cases: Use this when you need to directly use DSH’s file reading, search, or web search capabilities in an Agent outside a DSH environment (such as Claude Code).
  • Security notes:
    • The default allowlist contains only read-only, low-risk tools. Be cautious when adding write operations while modifying the configuration.
    • The server endpoint must be bound to 127.0.0.1 (loopback address). Do not bind it to 0.0.0.0 unless you fully trust the network environment.
  • Bidirectional communication: dsh-mcp-bridge currently only supports one-way exposure of “external client -> DSH.” If you need to connect to external MCP servers inside DSH, use the official @deepseek-ai/dsh-mcp-client plugin.

Conclusion

dsh-mcp-bridge enables DSH to function not only as a tool consumer but also as a tool provider within the MCP ecosystem. With simple configuration and an HTTP endpoint, DSH’s security capabilities can be reused across various Agents.