Skip to main content
Glama
Sign In
opencode-subagent-mcp

opencode-subagent-mcp

by sebstaq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to opencode-subagent-mcp

No user-submitted related servers found.

    Related Servers

    • Houtini LM

      EdwardNovikov861
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code and other MCP clients to delegate bounded tasks such as code review, boilerplate generation, commit messages, and format conversion to a local or cloud OpenAI-compatible LLM. It keeps the main model as architect while cutting token costs by sending files and prompts straight to the second model instead of into the orchestrator's context window.
      MIT

    • Houtini LM

      Pavelj43
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Code to delegate bounded coding and review tasks to local or cloud OpenAI-compatible LLMs, reducing token costs and providing a second model opinion. The main orchestrator retains planning and tool use while offloading drafting, code review, test stubs, documentation, and embeddings.
      MIT

    • Houtini LM

      Kerstin59718
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code or any MCP client to delegate bounded tasks such as code review, boilerplate, and documentation to local or cloud OpenAI-compatible LLMs. This reduces token usage by keeping large source files out of the main model's context while allowing results to be reviewed by the orchestrator.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a distinct lifecycle action: launch (agent), follow-up (send_message), await result (wait), abort (stop), enumerate (list). The overlap between wait (awaits a background agent) and send_message (resumes a finished agent and returns its report) is clearly disambiguated by their descriptions.

    Naming Consistency3/5

    Names mix conventions: send_message is verb_noun, while wait, stop, and list are bare verbs and 'agent' is a bare noun. All are readable, but there is no single predictable pattern across the set.

    Tool Count5/5

    Five tools cleanly cover the subagent lifecycle (launch, message, wait, stop, list) with no redundancy. This is well-scoped for the server's stated purpose.

    Completeness4/5

    The surface covers launch, resume, wait, stop, and list, which spans the full lifecycle. Minor gaps exist (e.g. no dedicated status/inspect or explicit cleanup of retained worktrees), but agents can work around them via list and send_message.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources