Skip to main content
Glama
cv588888888888888888888ju

dsh-web-mcp

by cv588888888888888888888ju
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to dsh-web-mcp

No user-submitted related servers found.

    Related Servers

    • MCP DSH Nexus

      tommilevs
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables permission-scoped MCP clients to interact with DeepSeek Harness Desktop over a local loopback HTTP bridge, including checking status, listing models/workspaces/sessions, reading bounded session history, and creating, sending, waiting for, or canceling chats. Access is restricted per bearer token and only exposes the tools and sessions granted to that token.
      MIT

    • dsh-ops-mcp

      Leawind
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP client to operate DeepSeek Harness sessions, execute tasks, and manage workspaces through an MCP server running inside the dsh process.
      MIT

    • dsh-as-mcp

      xiseliuli
      A
      license
      Not graded
      quality
      A
      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
      MIT

    • RemoraFish MCP

      howdeploy
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes authorized ChatGPT, DeepSeek, Kimi, and Grok web sessions to agents as MCP tools, including chat and local file attachments over HTTP or stdio.
      7
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Tool purposes are mostly distinct, but create_session and resume_session both establish a session for sending messages, and the difference (new vs existing) could confuse an agent without careful reading. Descriptions resolve the ambiguity, so only minor overlap remains.

    Naming Consistency5/5

    All tools share the dsh_ prefix and follow a clean verb_noun pattern: create_session, send_message, get_session_stats, resume_session, list_workspaces. The naming is perfectly consistent and predictable.

    Tool Count5/5

    With 5 tools, the server is well-scoped for session and workspace management. Each tool has a clear role, and the count is within the ideal range for a purpose-built MCP.

    Completeness3/5

    Core workflow is covered (create/resume, send, stats, list workspaces), but the surface lacks session deletion or a way to list existing sessions directly. These are notable lifecycle gaps that agents may hit when trying to manage or clean up sessions.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources