Skip to main content
Glama

Related Servers

Alternatives to all-agents-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      F
      maintenance
      Provides 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.
      11
      21
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Unified 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 npm
      19
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Orchestrates 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 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables 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

    B3.2/5.0

    Scored across 14 tools

    Disambiguation3/5

    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.

    Naming Consistency3/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues