dsh-session-bridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DSH_HOME | No | The DSH home directory. Defaults to ~/.dsh. The endpoint file is normally located at $DSH_HOME/session-bridge/endpoint.json. | ~/.dsh |
| DSH_SESSION_BRIDGE_ENDPOINT | No | Overrides the path to the endpoint file read by the MCP server. Set the same path on both sides when moving the file. Default is unset, in which case the MCP server uses DSH_HOME. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dsh_list_sessionsA | List Sessions of the running DeepSeek Harness app: id, title, agent preset, working directory, and whether a turn runs. |
| dsh_open_sessionA | Open a Session in the running app. By default it reuses the newest idle Session with the same preset and cwd. Set reuse to false for a new Session. |
| dsh_sendA | Send a user message to a Session. Returns afterSeq: pass it to dsh_wait and dsh_read to see only the new work. |
| dsh_waitB | Wait until the Session ends a turn after afterSeq, or until the timeout. |
| dsh_readA | Read caller prompts and assistant text messages of a Session with seq greater than afterSeq. Messages the app injects, tool calls, and thinking are not included. |
| dsh_cancelA | Interrupt the running turn of a Session. Queued messages stay queued. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: listing, opening, sending to, waiting on, reading from, and cancelling a session. The send/wait/read trio is a coordinated workflow but each step is unambiguous and descriptions clarify the afterSeq handoff.
All tools share a consistent dsh_ prefix and use a verb-first style (list_sessions, open_session, send, wait, read, cancel). The only minor deviation is that send/wait/read/cancel omit the noun, but the pattern is still predictable.
Six tools is well-scoped for a session bridge, covering the full interaction loop without redundancy. Every tool earns its place.
The surface covers listing, opening/reusing, messaging, waiting, reading, and interrupting sessions—a complete interaction lifecycle. Minor gaps like explicitly closing/deleting a session exist but agents can work around them via open with reuse=false.