all-agents-mcp
Related Servers
Alternatives to all-agents-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityAmaintenanceBridges multiple CLI coding agents (Codex, Cursor, OpenCode, Claude, Antigravity) into any MCP client, enabling delegation of prompts, parallel execution, and code review workflows.670 npmMozilla Public 2.0
- AlicenseNot gradedqualityDmaintenanceUnified CLI multiplexer for AI coding agents, enabling orchestration of multiple coding CLI tools through a single interface with session persistence, cost tracking, and MCP tool support.7 npm19MIT
- AlicenseNot gradedqualityBmaintenanceEnables orchestrating multiple AI CLI agents (Codex, Grok, Claude, etc.) via Claude Code, providing tools for dispatching tasks, broadcasting, debating, and managing jobs through a local MCP server.MIT
- AlicenseNot gradedqualityCmaintenanceOrchestrates and controls multiple AI agent CLIs (Claude-Code, Gemini-cli, etc.) via a unified MCP server, enabling complex multi-agent missions with shared memory and HTTP singleton architecture.287 npm2MIT

forge-orchestratorofficial
FlicenseNot gradedqualityAmaintenanceEnables orchestrating multiple AI coding tools (Claude Code, Codex CLI, Gemini CLI) on shared repositories with file locking, knowledge capture, task planning, and drift detection via an MCP server.161-
TDQS
Scored across 14 tools
The 'ask' family of tools (ask_all, ask_agent, delegate_task, collaborate, verify) has overlapping purposes, especially between ask_all/delegate_task (both parallel) and ask_agent/delegate_task (single vs auto-routing). Code and meta tools are clearly distinct, but the query tools could cause misselection without careful reading.
Names mix patterns: verb_noun (ask_agent, review_code), verb_with (debug_with, explain_with, refactor_with), standalone verbs (collaborate, verify), and noun-based (agent_health). While most follow a verb-leading style, the suffixes and noun-only names break predictability.
14 tools is near the upper bound but reasonable for a multi-purpose agent integration server that covers querying, code tasks, web fetch, and system info. Each tool has a role, though some redundancy in the 'ask' cluster makes the count feel slightly high.
The server covers the main workflows: asking agents, delegating, collaborating, verifying, code review/debug/explain/test/refactor, web fetch, and agent/model discovery. Minor gaps exist (e.g., no task cancellation or history retrieval) but they are not critical for core usage.