Skip to main content
Glama
Dokkabei97

all-agents-mcp

by Dokkabei97
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to all-agents-mcp

No user-submitted related servers found.

    Related Servers

    • CLI Agent MCP

      shiharuharu
      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

    • climux

      veithly
      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.
      5 npm
      19
      MIT

    • Roundtable AI MCP Server

      alexisbayrak023
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables a primary AI coding assistant to delegate work in parallel to multiple specialized AI CLI tools (Gemini, Claude, Codex, Cursor) sharing the same project context, then aggregates their findings into a single synthesized response. Runs locally as an MCP server with zero markup, using existing CLI tools, API keys, and subscriptions across 26+ IDE clients.
      -
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    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

    Resources