Skip to main content
Glama
ArthurHtr

opencode-hermes-mcp

by ArthurHtr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to opencode-hermes-mcp

No user-submitted related servers found.

    Related Servers

    • Local Codex Bridge

      xiaozhe611317
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables external AI supervisors to oversee and steer native Codex through MCP, including thread and turn management, observation, interruption, approval responses, runtime status, and checkpointing.
      MIT

    • pipe-opencode

      artur-matkowski
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables inspection and control of a running OpenCode TUI session, including live pane capture, prompt injection, interrupting turns, and blocking waits for session state changes.
      MIT

    • dsh-mcp

      Moer2831
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets Claude Code, Codex, or any MCP client drive DeepSeek Harness as a long-lived coding agent: starting and resuming conversations, dispatching tasks in the background, streaming live output and reasoning stats, interjecting or interrupting mid-turn, handling approval prompts, and collecting results later. Sessions persist by ID, so work survives process restarts and can be handed back to a DSH GUI when needed.
      479 npm
      15
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct phase of the OpenCode lifecycle: running/resuming tasks, answering questions, deciding permissions, aborting, inspecting, and listing sessions. The two input-resolution tools are clearly separated by kind (question vs permission). No meaningful overlap exists.

    Naming Consistency3/5

    All tools share the opencode_ prefix, which helps, but the second element mixes verbs (run, answer, abort, inspect) with nouns (permission, sessions). There is no consistent verb_noun pattern, though the names remain readable and predictable enough within the server.

    Tool Count5/5

    Six tools cover the delegated-agent interaction loop without redundancy. Each tool earns its place, and the set is neither bloated nor too thin for the server's purpose.

    Completeness4/5

    The core lifecycle is well covered: start/resume tasks, respond to questions, grant or reject permissions, abort, inspect, and list sessions. The main gap is that agents cannot discover the available agent list through a tool, though generic agents like build/plan provide a usable fallback.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources