Skip to main content
Glama
tonytanglab

dsh-relay

by tonytanglab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to dsh-relay

No user-submitted related servers found.

    Related Servers

    • dsh-codex-mcp

      Zbrooklyn
      A
      license
      Not graded
      quality
      C
      maintenance
      Launches the official Codex CLI as a persistent MCP server so DeepSeek Harness can invoke Codex models without storing or transmitting ChatGPT credentials to third parties.
      MIT

    • codex-mcp

      alvarosw
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.
      9
      10 npm
      MIT

    • web-gpt-agent-core

      dbc-hbin
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects ChatGPT Web to a local development environment, enabling file reads and patches, shell execution, plan updates, and isolated worktree coordination through permissioned MCP tools.
      3
      MIT

    • dsh-cli-mcp

      minmax
      A
      license
      A
      quality
      C
      maintenance
      Delegates coding tasks to the locally installed DeepSeek Harness CLI, enabling MCP clients to run prompts through dsh and receive results with exit code and timing.
      1
      MIT

    • Codex Local Gateway

      sleda
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables ChatGPT Web or another MCP client to inspect and develop a local workspace, read local Codex task history, and use the complete installed XcodeBuildMCP catalog through a small set of stable tools.
      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

    B3.4/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools target distinct resources and actions (runs vs services vs workspaces), and the descriptions carefully differentiate get_run, wait_run, get_run_summary, and list_runs. The main ambiguity is the intentional status_run alias for get_run, plus start_run/start_review share similar task-parameter language, though their permission/preset distinction is clear.

    Naming Consistency4/5

    The overwhelming majority follow snake_case verb_noun names like list_runs, start_service, cancel_run, and wait_run. The exceptions are bare doctor and setup_doctor, which break the verb_noun pattern but do not introduce mixed casing styles.

    Tool Count3/5

    25 tools is at the high end of the borderline range, and many are needed for the run/relay lifecycle. Still, a deprecated alias (status_run), several setup/reconcile helpers, and notification/operation readers make the surface feel heavier than necessary.

    Completeness4/5

    The run lifecycle is well covered: create, review, reply, steer, get, wait, cancel, list, and reconcile. The gaps are minor—there is no explicit way to delete/forget a workspace session or run, and workspace management is read-only—but the core workflows have no dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources