Skip to main content
Glama
shiiman

multi-agent-mcp

by shiiman

Related Servers

Alternatives to multi-agent-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    C2.9/5.0

    Scored across 90 tools

    Disambiguation3/5

    Many tools have clear distinct purposes, but there is significant overlap in areas like task management (create_task, enqueue_task, assign_task_to_agent, send_task) and memory retrieval (retrieve_from_memory, search_memory_archive, get_memory_entry). Also cleanup_workspace and cleanup_on_completion overlap, and check_gtr_available/check_gtrconfig are confusingly similar.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (get_, list_, create_, update_, delete_, remove_, send_, etc.). Minor deviations exist such as 'merge_completed_tasks' (verb_adjective_noun) and 'monitor_and_recover_workers' (compound verb) but these are understandable.

    Tool Count1/5

    90 tools is an extremely high count. Even for a multi-agent orchestration system, this is far beyond what an agent can reasonably navigate. The count is justified by the breadth of the domain, but it represents a severe cognitive load and should be split into multiple focused servers.

    Completeness4/5

    The domain coverage is remarkably thorough: agent lifecycle, task lifecycle, worktree management, messaging, memory, health checks, screenshots, cost tracking, and model profiles. Minor gaps include no explicit update_agent or update_worktree tools, but most operational cycles are complete.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive