Skip to main content
Glama

Related Servers

Alternatives to opencode-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables Claude Code to dispatch opencode CLI tasks as background processes with immediate task handle return, status polling, and result retrieval, avoiding tmux and log parsing issues.
      6
      15 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables an orchestrator like Claude Code to hand coding work off to Cursor SDK agents, run as detached background jobs that survive the session and can be listed, inspected, steered, resumed, or stopped. Agents are asynchronous and reusable across follow-up turns, letting expensive frontier models delegate cheaply without blocking or paying to read the results.
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables asynchronous task delegation between Claude Code and Codex CLI through MCP tools, allowing either AI agent to request the other to perform tasks and monitor progress.
      5 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents like Claude Code or Codex to delegate tasks to a DeepSeek Harness subagent with its own context window, providing tools for task delegation, result waiting, continuation, and supervision with sandboxed execution.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables an interactive Claude Code session to delegate blocking tasks to headless pi and OpenCode workers, and lets all three peers exchange messages and list paired sessions over a shared local file bus. It exposes 18 tools covering sync/async asks, steering, abort, session lifecycle, state inspection, and cross-agent messaging.
      231 npm
      1
      MIT

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action: server lifecycle (start/stop), task lifecycle (start, wait, get result, get status), and agent listing. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent 'opencode_' prefix with verb_noun pattern (e.g., start_server, get_task_result). No mixing of conventions.

    Tool Count5/5

    Seven tools cover core server and task management appropriately. Neither too sparse nor too bloated for the domain.

    Completeness4/5

    Covers server start/stop, agent listing, and task delegation with status/result retrieval. Missing a cancel_task or list_tasks tool, but core workflows are well-supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues