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 gradedqualityFmaintenanceEnables a primary coding agent to delegate bounded implementation and repair tasks to a local OpenAI-compatible model that edits a copy of the project, runs configured checks, and returns artifacts for review. Exposes stdio tools for capability discovery, task submission, progress polling, artifact reading, and cancellation.MIT
- AlicenseNot gradedqualityCmaintenanceExposes DeepSeek Harness's coding agent as a model backend via MCP, with user-confirmed task execution and self-inspection/config-patch tools.12 npmMIT
- 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.62 npm13MIT
- 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.141MIT
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes: task creation, cancellation, continuation, and interaction replies are unambiguous. However, zcode_status, zcode_result, and zcode_events are three separate read tools over task state, and zcode_default_model vs zcode_model_catalog could momentarily overlap, though the descriptions do distinguish them.
All tools share a consistent zcode_ prefix and snake_case, which makes the set predictable. The minor deviation is that some names are nouns (zcode_task, zcode_status, zcode_result) while others are verb-led (zcode_continue, zcode_cancel, zcode_set_default_model), so the pattern is readable but not a strict verb_noun convention.
Twelve tools is well within a sensible range and each earns its place, covering task lifecycle, event streaming, interaction handling, model configuration, and diagnostics without redundancy.
The surface covers the full task lifecycle (create, status, result, continue, cancel), event streaming, permission/input replies, model default read/set/clear, catalog, and a doctor diagnostic. A minor gap exists, such as no explicit task listing or deletion/cleanup operation, but core workflows are covered.