Skip to main content
Glama
teodorgross

opencode-mcp-bridge

by teodorgross
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to opencode-mcp-bridge

No user-submitted related servers found.

    Related Servers

    • mcp-opencode

      shreeraman96
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets an AI coding agent delegate implementation work to the OpenCode CLI, choosing an explicit provider + model on every call.
      3
      MIT

    • opencode-mcp-bridge

      Dheerax
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that lets any AI tool delegate tasks to the OpenCode CLI as a subagent, with multi-session orchestration, event tracking, and task contracts.
      28
      8 npm
      1
      MIT

    • open-subagent-mcp

      g2zz
      A
      license
      A
      quality
      D
      maintenance
      A local MCP server that delegates tasks to a subagent runtime via OpenAI-compatible interfaces, enabling file operations, command execution, and rollback of local file changes.
      5
      MIT

    • AgentHub

      stojandev
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that orchestrates multi-agent coding teams by spawning workers, delegating tasks, and managing session lifecycles through an external MCP client.
      MIT

    • local-vibes

      OpenSourceWTF
      F
      license
      A
      quality
      B
      maintenance
      A generic OpenAI-compatible subagent MCP server that lets Claude Code delegate coding grunt-work to a local model via a tool-calling agent loop, with configurable concurrency and backend.
      1
      -
    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

    A4.1/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the opencode lifecycle: server health, configuration, run creation, monitoring, cancellation, and result retrieval. While several tools return run information (status, result, messages, diff, todos), their descriptions clearly differentiate the exact data each returns.

    Naming Consistency4/5

    All tools share the consistent 'opencode_' prefix and snake_case format. The naming mixes nouns for query tools (opencode_result, opencode_todos) and verbs for action tools (opencode_dispatch, opencode_wait), which is a reasonable convention, though not a uniform verb_noun pattern.

    Tool Count4/5

    With 15 tools, the server sits at the upper edge of a well-scoped set. Each tool serves a clear purpose in managing opencode runs, covering dispatch, waiting, follow-up, cancellation, and detailed inspection, without unnecessary redundancy.

    Completeness5/5

    The tool set provides comprehensive coverage of the opencode run lifecycle: creating runs, following up, waiting, answering questions, cancelling, and retrieving results, messages, diffs, todos, and status. Configuration tools for models, agents, and health are also included, leaving no obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources