dsh-web-mcp
Related Servers
Alternatives to dsh-web-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA stdio MCP server that wraps DeepSeek Harness's local /api into 9 tools, letting any standard MCP client create or adopt named dsh sessions, dispatch task briefs, poll asynchronously, and retrieve auditable per-turn results. It also enforces pre-validated model allowlists, workspace/alias boundaries, and a persistent session ledger, so agents can collaborate across harnesses without modifying dsh or installing client plugins.MIT
- AlicenseAqualityCmaintenanceA local STDIO MCP server that bridges Codex to the official DeepSeek Harness (DSH) Web Host, enabling supervised DSH collaboration through session management, delegation, and monitoring tools.1312MIT
- AlicenseNot gradedqualityCmaintenanceBridges a planning and review client to DeepSeek Harness Desktop over local stdio MCP, letting users submit staged tasks with explicit goals, scope, and acceptance criteria for execution inside native DSH sessions, models, and approval boundaries. Exposes task submission, waiting, evidence retrieval, review, continuation, cancellation, and recovery tools so results are judged against traceable evidence from the current run.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables Codex to create, resume, and control DeepSeek Harness sessions through a local MCP stdio bridge using ACP, including listing, messaging, cancelling, and closing sessions.62MIT
- AlicenseNot gradedqualityBmaintenanceEnables any MCP client to operate DeepSeek Harness sessions, execute tasks, and manage workspaces through an MCP server running inside the dsh process.730 npm1MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.