dsh-zcode-bridge
Related Servers
Alternatives to dsh-zcode-bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables external agents to delegate coding tasks to a local zcode/GLM coding agent, with multi-turn sessions, model selection, and task cancellation.3MIT
- AlicenseNot gradedqualityCmaintenanceExposes DeepSeek Harness's coding agent as a model backend via MCP, with user-confirmed task execution and self-inspection/config-patch tools.MIT
- AlicenseNot gradedqualityAmaintenanceExposes DeepSeek Harness agent capabilities as an MCP server, letting any MCP client drive Harness to execute real coding tasks with structured results, context isolation, and parallel execution.115 npm12MIT
- AlicenseNot gradedqualityBmaintenanceExposes DeepSeek Harness agent capabilities over MCP so any MCP client can delegate real coding work to a running agent with its full toolset (bash, filesystem, todo, web). Turns are dispatched asynchronously into sessions and then tracked through status, tail, wait, cancel, compact, and rename tools, with the session log as the source of truth so results survive restarts.MIT
- AlicenseAqualityAmaintenanceEnables programmatic control of the Z.ai/Zhipu desktop AI coding agent by spawning and owning its headless agent runtime and speaking the ZCode Protocol over stdio, rather than simulating a user. Exposes tools to run and steer chat sessions, inspect conversations and file changes/rewinds, and manage settings, providers, plugins, MCP servers, automations and approvals under a deny-by-default policy with mandatory read-back verification.14MIT
- AlicenseNot gradedqualityBmaintenanceLets any MCP-capable coding harness (Cursor, Claude Code, Codex, Gemini CLI, VS Code/Copilot, opencode, and others) hand a self-contained task to a real, isolated DeepSeek Harness process that works in a chosen workspace with its own context window, model, and toolchain, then returns the final answer. Exposes task submission with time estimates and acceptance criteria, status polling with live progress and process-tree telemetry, graceful cancel and forced kill of whole process trees, and a health probe reporting concurrency, deadlines, and recent jobs.MIT
TDQS
Scored across 13 tools
Each tool targets a distinct bridge concern: task lifecycle, model defaults, diagnostics/catalog, and permission/input replies. zcode_status, zcode_events, and zcode_result are separated by execution status, progress stream, and final normalized result, so misselection is unlikely.
All names use the same zcode_ snake_case prefix with predictable noun/verb phrases. Even where verbs are implicit, such as zcode_default_model or zcode_task, the convention is internally consistent.
Thirteen tools fit the bridge scope: a full task lifecycle, model configuration, diagnostics, and interaction handling. The temporary progress probe is extra but not excessive.
Core lifecycle and configuration are covered, including create, monitor, continue, cancel, result, and permission replies. Minor gaps exist for task enumeration/history and explicit artifact/diff retrieval, though the latter is intentionally left to the master agent.