Introduction

The DeepSeek Harness (DSH) Agent Communication Protocol (ACP) typically returns only the final result, so developers cannot observe an agent’s reasoning process or tool calls in real time. The dsh-streaming-mcp-bridge plugin bridges Harness’ real-time session.event and session.status streams, exposing reasoning, tool calls, and status updates to external clients or integration tools.

What It Is

This is a community-maintained DSH plugin (owner: yabolee-kkk). It bridges Harness’ real-time session stream to external MCP clients or ACP adapters (such as Feishu), addressing the issue that static ACP responses cannot show the process.

Core Features

  • Streamable HTTP MCP: Supports notifications/progress, allowing real-time task progress monitoring via the MCP protocol.
  • ACP Adapter for Feishu: Pushes reasoning, tool calls, and status updates to Feishu in real time, facilitating team collaboration.
  • Real-time Streaming: Directly exposes session.event and session.status.

Installation and Enablement

Install it as a DSH bundle plugin into the Web profile:

dsh plugin --profile web add dsh-streaming-mcp-bridge

Start DSH Web after installation:

dsh web

Configuration and Authentication

The plugin listens by default on http://127.0.0.1:3477/mcp. It is recommended to set a Bearer token for authentication:

export DSH_STREAMING_MCP_TOKEN="your-secret-token"

Configuration items such as host, port, and authTokenEnv can be overridden via the profile’s cordis.patch.yml.

MCP Usage

Use curl to verify the MCP connection. First, initialize a session to obtain the Mcp-Session-Id, then open the GET SSE stream, and finally call the dsh_run_stream method to view notifications/progress:

curl -X POST http://127.0.0.1:3477/mcp \
  -H 'Authorization: Bearer TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

ACP / Feishu Mode

The plugin supports ACP mode and can be integrated with cc-connect or Feishu. In the cc-connect configuration, set type to acp and specify the Harness JSON-RPC runtime path (by default, the source path under DSH_HARNESS_HOME is used). In Feishu, each reasoning step, tool call, and status update is placed in its own code block, while the final answer is placed outside the code blocks.

Security and Notes

  • MCP listens on 127.0.0.1 by default; do not expose it directly to the public internet.
  • Use Bearer token authentication.
  • dsh_run_stream instructs Harness to execute real tasks; grant access only to trusted users.
  • Node.js >= 22 is required.

Conclusion

By introducing streaming, this plugin fills a gap in process visibility within the DSH ecosystem. View the source code or submit issues: GitHub