opencode-bridge
Related Servers
Alternatives to opencode-bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables delegating Claude Code subagent tasks to cheaper opencode models, while keeping the main Claude Code session connected directly to Anthropic.51,354 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables 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.-
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to delegate mechanical tasks (summaries, boilerplate, reformatting) to local models running in LM Studio.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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
- AlicenseAqualityBmaintenanceEnables Claude Code to delegate software-engineering tasks to OpenCode agents working in the same workspace.739 npm1MIT
- FlicenseNot gradedqualityDmaintenanceLets Claude Code offload cheap, mechanical tasks to opencode's free models for codebase summaries, exploration, web research, and bulk edits, saving paid tokens.-
TDQS
Scored across 8 tools
Each tool has a clearly distinct lifecycle role: delegate starts, continue follows up, task_progress inspects, abort pauses, end deletes, list_tasks recovers, list_models selects, bridge_health validates. No two tools could be confused for the same action.
Most tools follow verb_noun (delegate_task, continue_task, abort_task, end_task, list_tasks, list_models), but task_progress and bridge_health break the verb-first pattern. The names remain readable and predictable, so the inconsistency is minor.
Eight tools is well-scoped for a delegation bridge: the full session lifecycle (create, resume, monitor, abort, delete, list) plus model discovery and health checking. Every tool serves a necessary purpose with no redundancy.
The tool surface covers the complete delegation workflow: starting, continuing, inspecting, aborting, ending, listing, model selection, and health verification. There are no obvious missing operations for the stated purpose of managing external coding task delegations.