agent-bridge
Related Servers
Alternatives to agent-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that enables Claude Code to delegate tasks to Codex for real-time collaborative code generation and execution.4 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables Claude Code to communicate with other Claude Code agents over HTTP, allowing users to ask questions about remote codebases or delegate coding tasks.MIT
- AlicenseAqualityBmaintenanceAn MCP server for running Claude Code and the Codex CLI as a pair: Claude drives, and hands self-contained tasks to Codex as background jobs.8MIT
- AlicenseNot gradedqualityDmaintenanceA multi-agent MCP server that enables AI coding agents (Claude Code, Codex CLI, Gemini CLI) to communicate with each other.MIT
- AlicenseNot gradedqualityCmaintenanceA MCP server that enables Claude Code to delegate coding tasks to Codex via the MCP protocol, with task management, security checks, and result verification.18 npmMIT
- FlicenseNot gradedqualityAmaintenanceMCP server that bridges coding agents (Claude Code, Codex, Gemini CLI) via ACP for pair programming, enabling agents to consult each other as tools.3-
TDQS
Scored across 1 tool
Only a single tool exists, so there is no possibility of confusion with other tools. The delegate tool's purpose is clearly described as handing tasks to another agent.
With only one tool, naming consistency is trivially maintained. The name 'delegate' is a clear, imperative verb that matches its action.
The server has exactly one tool, which is borderline and feels thin for a 'bridge' concept. While it covers the core delegation operation, a single tool is at the low end of acceptable scoping.
The delegate tool covers the primary task of handing work to another agent, but there are no tools to discover available agents, check statuses, or manage the bridge. This leaves notable gaps for a full agent-bridge lifecycle.