Log inSubmit server
Dsh MCP Btwy logo

Dsh MCP Btwy

Expose DeepSeek Harness sessions, prompts, approvals, questions, and tools to MCP clients over authenticated HTTP or stdio.

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install Dsh MCP Btwy

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "dsh-mcp-btwy": {
      "command": "npx",
      "args": [
        "-y",
        "dsh-mcp-btwy"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y dsh-mcp-btwy

DeepSeek Harness MCP endpoint is unavailable: no endpoint is configured. Start the DSH app (or load the dsh-mcp-server plugin) and retry.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked Today.

Overview

dsh-mcp-btwy connects MCP clients to a running DeepSeek Harness (DSH) host, allowing agents to create, continue, inspect, wait on, and cancel DSH sessions. It serves requests through Streamable HTTP or a stdio bridge and attributes sessions to their calling agents. Use it when another harness needs to operate DSH locally, share an endpoint across harnesses, or inspect pending approvals and questions.

Use cases

  • Drive DeepSeek Harness sessions from Claude Code, Cursor, or Codex
  • Continue agent work while preserving its DSH workspace and context
  • Inspect pending approvals and unanswered user questions
  • Share one authenticated DSH endpoint across multiple agent harnesses
  • Read bounded portions of large session histories

Key features

  • Streamable HTTP and stdio MCP connectivity
  • Session creation, continuation, waiting, cancellation, and querying
  • Bounded, paginated session-history access
  • Approval and user-question inspection and response
  • Caller attribution with optional owner-only restrictions
  • Lazy or full internal DSH tool surfaces

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9h ago via OSV.dev · dsh-mcp-btwy (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
npm downloads2.9kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.

How Dsh MCP Btwy works

What dsh-mcp-btwy does

dsh-mcp-btwy publishes a Model Context Protocol interface for a running DeepSeek Harness host. External agents can start work in DSH, continue an existing session with its context and workspace, wait for completion, cancel an active turn, and read conversation history.

The interface also exposes session discovery and coordination features. Clients can list sessions with pagination, search for bounded text fragments, and read head, tail, or outline windows with cursors and response budgets. Request inspection surfaces pending approvals and unanswered user questions, while dedicated operations can answer them when those controls are enabled.

A session can ask another session a numbered question and wait for a reply without waking the target session. The server also supports opening a session in the DSH web interface and synchronizing work in the same workspace.

How it works

The plugin runs inside DSH and forwards MCP calls to DSH services such as its session controller, session query layer, and tools. Clients may connect through Streamable HTTP or stdio. For HTTP, the endpoint publishes a URL and bearer token in $DSH_HOME/mcp/dsh-mcp-endpoint.json; the file is created with restrictive permissions.

Long-running calls use an event-stream response after ten seconds. The server sends response headers promptly, emits periodic keep-alive comments, and returns the final JSON-RPC result when the operation finishes. This supports waits that last several minutes without depending on a client’s initial response-header timeout.

Caller identity is derived from request metadata such as headers, MCP clientInfo, or User-Agent. Sessions are recorded under that identity, allowing multiple harnesses to use one endpoint. With restrictToOwner enabled, callers can access only sessions they created.

Setup and configuration

Install the dsh-mcp-btwy package from the DSH Plugins page or with the DSH plugin command. A source checkout can also be installed through the plugin manager or by supplying its repository path.

After installation, read the generated endpoint file and configure an MCP client with the published URL and bearer token. A typical HTTP connection uses an Authorization: Bearer <token> header. The endpoint binds to 127.0.0.1 by default; changing the host is an explicit deployment choice.

The plugin page controls server behavior, including whether the internal tool surface is lazy or full, sidebar grouping, busy-session delivery, progress synchronization, and message presentation. Deployment presets named delegate, strict, and observer can populate fields that have not been set explicitly.

Tools and capabilities

  • Run a prompt and create a DSH session with dsh_run_prompt.
  • Continue, wait for, cancel, or ask questions of sessions with the corresponding DSH session operations.
  • List, search, and window session history instead of returning an unbounded transcript.
  • Inspect and answer pending approvals or user questions with request operations.
  • Open a selected session in the DSH web GUI.
  • Use a lazy three-tool internal entry point—dsh_mcp_tools, dsh_mcp_open, and dsh_mcp_call—or register the full tool surface.
  • Deliver inter-session messages and report workspace progress.

Limitations and notes

The endpoint requires a bearer token for every request and does not accept tokens in URL query parameters. Keep the generated endpoint file protected and connect only harnesses that you trust: calls run against the local DSH installation with the user’s permissions.

Owner restrictions can reject cross-session guest calls. Approval-answering features should be enabled deliberately because delegating approval decisions can grant sandbox permissions. Internal DSH calls remain constrained by the invoking session’s sandbox and workspace.

The plugin is host-side and has no runtime dependencies. Its behavior depends on the DSH service contract rather than importing DSH packages. DSH’s own MCP client can connect to the endpoint, in addition to the plugin’s internal tools.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Dsh MCP Btwy

dsh-mcp-btwy is an MCP server that connects MCP clients to a running DeepSeek Harness host. Its main tools create and continue sessions, wait for or cancel work, read session history, inspect pending approvals and questions, answer requests, and open sessions in the DSH web interface.

Install dsh-mcp-btwy from the DSH Plugins page or with the DSH plugin command. You can also install a cloned repository through the plugin manager or by providing its path to the plugin installer.

Connect through Streamable HTTP or stdio. For HTTP, read the URL and token from `$DSH_HOME/mcp/dsh-mcp-endpoint.json`, then configure the client with the URL and an `Authorization: Bearer <token>` header.

Yes. Cursor is named as a supported MCP client for dsh-mcp-btwy. Configure it with the published HTTP endpoint and bearer token, or use the available stdio bridge.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDsh MCP Btwy AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/dsh-mcp-btwy?style=directory)](https://allmcps.com/mcp/dsh-mcp-btwy)
HTML Embed
<a href="https://allmcps.com/mcp/dsh-mcp-btwy"><img src="https://allmcps.com/api/badge/dsh-mcp-btwy?style=directory" alt="Dsh MCP Btwy on AllMCPs" /></a>