Skip to main content
Glama
dsh-inbox-mcp

dsh-inbox-mcp

by johnx438-hub

Related Servers

Alternatives to dsh-inbox-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a running DeepSeek Harness as an MCP endpoint so any other agent or script can create workspaces and sessions, hand coding tasks to the DSH agent, read and write files, run shell commands, and invoke permitted harness tools under the same sandbox, transcript, and permission policy as the DSH UI.
      1,888 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables any MCP client to operate DeepSeek Harness sessions, execute tasks, and manage workspaces through an MCP server running inside the dsh process.
      730 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables DSH agents on the same LAN to exchange queued messages through a shared hub, wait for replies, check peer presence, and optionally wake the target session.
      129 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Lets MCP clients such as Codex dispatch tasks to a live DSH session, wait for or poll results by task ID, and list available sessions and registered workspaces, targeting a project by its absolute workspace path instead of a session ID so existing sessions are reused or created automatically.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets Claude Code, Codex, or any MCP client drive DeepSeek Harness as a long-lived coding agent: starting and resuming conversations, dispatching tasks in the background, streaming live output and reasoning stats, interjecting or interrupting mid-turn, handling approval prompts, and collecting results later. Sessions persist by ID, so work survives process restarts and can be handed back to a DSH GUI when needed.
      16
      MIT

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    dsh_inbox_status reads/polls session state while dsh_inbox_deliver writes/sends a prompt; there is no overlap in their actions. An agent can easily choose the right tool based on whether it needs to observe or act.

    Naming Consistency4/5

    Both tools share the clear dsh_inbox_ prefix and use snake_case, so they are instantly recognizable as part of one server. The minor deviation is that one name uses a noun (status) and the other uses a verb (deliver), rather than a uniform verb_noun pattern.

    Tool Count3/5

    Two tools is at the low end of the acceptable range and feels thin for a general MCP surface. For the narrow status-and-deliver purpose the count is reasonable, but it is borderline rather than solidly well-scoped.

    Completeness4/5

    The core poll-and-deliver loop is covered: status tells whether the session is ready or busy, and deliver handles the different queueing modes. Mino gaps exist around inspecting queued messages or listing multiple sessions, but agents can generally work around these.