A
licenseNot graded
qualityA
maintenanceAn 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
by Dheerax
Related Servers
Alternatives to opencode-mcp-bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA 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.5MIT
- AlicenseAqualityBmaintenanceThis MCP server enables LLM hosts to plan large tasks and delegate subtasks to specialized local CLI agents, such as Codex and Claude Code, using tools like delegate_task and get_agent_roster.2MIT
- AlicenseAqualityCmaintenanceMCP server that delegates code writing, editing, and execution to OpenCode, allowing AI assistants to focus on decision-making.17MIT
- FlicenseAqualityBmaintenanceAn MCP server that provides OpenCode's native tools (file read/write/edit, search, shell, web fetch/search, and more) to compatible Code CLIs like Codex and Claude Code.1123-
- FlicenseNot gradedqualityDmaintenanceA lightweight MCP server that enhances AI agents with tools for codebase analysis, task delegation to sub-agents, multi-agent coordination through chatrooms, and project todo management.-
TDQS
B3.3/5.0
Scored across 28 tools
Disambiguation5/5
Each tool clearly targets a distinct aspect of session or server management: health vs status vs context vs diff serve different query depths, send vs command vs interrupt handle different input methods, and checkpoint/retry/list_checkpoints form a clear lifecycle. The only near-overlap (health vs server_health) is explicitly disambiguated in the description.
Naming Consistency4/5
All tools share the opencode_ prefix and use snake_case, providing a consistent style. However, the pattern mixes bare nouns (health, status, context) with verb-first forms (set_model, list_checkpoints, server_restart), so it is not a strict verb_noun pattern throughout.
Tool Count3/5
28 tools is on the heavy side, straddling the 'too many' threshold. The breadth is justified by the complex session-lifecycle and server-management domain, but the count exceeds the typical well-scoped range and may introduce selection overhead for agents.
Completeness5/5
The surface covers the full session lifecycle (start, read, interrupt, kill), checkpointing (save, list, retry), batch operations, configuration, and server health. No obvious dead ends or missing operations for the stated purpose of bridging to OpenCode.
Maintenance
ActivitySlowing
ResponsivenessNo issues