MCP Model Bridge
Related Servers
Alternatives to MCP Model Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables a primary coding agent to delegate bounded implementation and repair tasks to a local OpenAI-compatible model that edits a copy of the project, runs configured checks, and returns artifacts for review. Exposes stdio tools for capability discovery, task submission, progress polling, artifact reading, and cancellation.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to offload bounded, read-heavy tasks to external agent CLIs (agy, opencode, copilot) with preflight validation, circuit breakers, and a local dashboard for monitoring delegation and subagent activity.39 npmMIT
- FlicenseAqualityDmaintenanceExposes tools to list, run, and inspect GitHub Actions workflows locally via act, enabling debugging and fixing failures through an agent loop.3-
- AlicenseNot gradedqualityAmaintenanceLets you define reusable, task-specific coding agents in Markdown files and invoke them from any MCP-compatible client, running each one through a chosen coding CLI backend and returning the result to the same conversation. Supports shared backend and model settings, permission modes, and optional session continuity so an agent can continue work across multiple calls.338 npmMIT
- AlicenseAqualityBmaintenanceEnables delegating coding tasks to Cursor Cloud Agents from Claude Code, Codex, or Grok, with scoped repository access, progress monitoring, follow-ups, and result reporting.23MIT
- AlicenseAqualityFmaintenanceEnables Codex CLI to delegate tasks to file-based specialized agents with isolated execution, auditability, and CI-friendly validation.4161MIT
TDQS
Scored across 2 tools
list_agents is a read-only introspection operation and run_agent is an execution operation, targeting entirely different actions on the same domain. There is no plausible way for an agent to confuse the two.
Both tools follow a clean verb_noun snake_case pattern (list_agents, run_agent) with the noun 'agent' consistent across the set. Fully predictable.
Two tools is thin even for a narrow bridge surface; a discovery call plus a single execution call leaves little room for inspecting, validating, or managing runs. Still, both tools clearly earn their place given the stated purpose.
The pairing of discover-agents and execute-agent covers the core read/run lifecycle, and run_agent returns the model actually used, closing the routing-verification loop. Gaps are minor and largely handled outside the server (agent definitions live in the host project), though there is no status, cancel, or batch execution path.