agent-mcp-hub
Related Servers
Alternatives to agent-mcp-hub
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceBridges any MCP client (like Claude Code, Zed, VS Code) to any ACP coding agent, enabling multi-agent orchestration from a single chat interface.241409Apache 2.0
- AlicenseBqualityFmaintenanceEnables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.141314MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that bridges CLI coding agents like Claude Code, Codex, opencode, and Antigravity into any MCP client, enabling synchronous and asynchronous task execution, follow-up input, and a structured code review tool.1571MIT
- AlicenseAqualityFmaintenanceProvides unified access to multiple CLI AI agents (Codex, Gemini, Claude, and OpenCode) through a single MCP interface with real-time task monitoring, enabling specialized code analysis, UI design, implementation, and prototyping workflows.1121MIT
- AlicenseNot gradedqualityCmaintenanceMCP bridge for calling local coding-agent CLIs (Codex, Claude) from another agent, enabling bounded tasks like code review, verification, and bug hunting.MIT
- 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.2-
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: ping for liveness, list_agents for availability, codex and claude for running specific CLIs, run_all for fan-out, and review_change for the review workflow. Even though codex and claude are similar, the tool name explicitly selects the target CLI, eliminating ambiguity.
Naming is a mix: verb_noun (list_agents, review_change), product names (codex, claude), a single word (ping), and run_all. While readable and following a lowercase snake_case pattern, the lack of a consistent verb_noun style and the use of proper nouns for some tools makes the naming somewhat inconsistent.
With 6 tools, the server is well-scoped for its purpose of wrapping coding-agent CLIs. Each tool addresses a distinct need—health check, discovery, individual execution, fan-out, and review—without redundancy or bloat.
Core workflows are covered: running codex or claude, running all agents, and reviewing changes. However, list_agents implies the server can discover arbitrary agents, yet there is no generic 'run agent by name' tool, only the hardcoded codex and claude. This gap could prevent users from running other agents that list_agents might report as available.