A
licenseA
qualityB
maintenanceEnables Codex and Claude Code to delegate implementation, research, debugging, and long-log work to DeepSeek Harness, then observe, continue, or cancel those sessions without leaving the primary workflow.
15
1
MIT
dsh-web-bridge-mcp
by yy2511
Related Servers
Alternatives to dsh-web-bridge-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables Codex to supervise long-running DeepSeek Harness sessions through MCP, providing tools for progress monitoring, handoffs, and artifact management while keeping the host independent.MIT
- AlicenseNot gradedqualityAmaintenanceEnables external MCP clients to drive DeepSeek Harness agents for real coding tasks, providing tools for task execution and queueing, session management, sandboxed file access, preset switching, and usage statistics.564 npm5GPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables web ChatGPT sessions to submit discussion results back to the original Codex task via MCP, allowing the task to continue after the web interaction completes.MIT
- AlicenseNot gradedqualityBmaintenanceEnables dispatching work to DeepSeek Harness agents from Claude Code/Codex, with native progress UI, tier policy, and vision/image generation through MCP tools.569 npm153MIT
- FlicenseAqualityCmaintenanceEnables MCP clients like Codex CLI and Claude Code to delegate tasks to a local DeepSeek Harness (dsh), with native Web transport for visible progress, model selection, and persistent long-running jobs, plus an ACP-compatible transport.6-
TDQS
A4.1/5.0
Scored across 10 tools
Disambiguation5/5
Each tool targets a distinct phase of the session lifecycle: discovery, history reading, connection/auth, creation, messaging, waiting, result retrieval, and cancellation. Even the two session-finding tools are clearly separated by metadata filtering versus keyword/content search.
Naming Consistency4/5
All tools share the dsh_ prefix and use snake_case, which gives a predictable pattern. Minor deviations exist: dsh_result is a noun rather than a verb_action, and several tools like dsh_connect, dsh_wait, and dsh_cancel lack a noun object.
Tool Count5/5
Ten tools is a well-scoped size for a session-delegation bridge. Each tool covers a meaningful operation without redundancy or bloat, and the count aligns with the server's focused purpose.
Completeness4/5
The core delegation lifecycle is well covered: connect, authenticate, create/find sessions, send, wait, retrieve results, read history, and cancel. The main gap is the lack of a delete/close-session tool, which leaves cleanup to external session management.
Maintenance
ActivityMaintained
ResponsivenessNo issues