Skip to main content
Glama
wyn0001

AI Collaboration MCP Server

by wyn0001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to AI Collaboration MCP Server

No user-submitted related servers found.

    Related Servers

    • kanban-mcp

      SimonBlancoE
      A
      license
      Not graded
      quality
      D
      maintenance
      Transforms Claude into an autonomous development team with architect, agent, and QA roles, enabling automated sprint execution, task management, and continuous learning.
      6 npm
      MIT

    • Gemini Collaboration MCP

      henry2craftman
      A
      license
      B
      quality
      D
      maintenance
      Enables Claude to collaborate with Gemini for code reviews, second opinions, and iterative software development. It facilitates multi-step workflows including PRD creation and code generation through an AI orchestration framework.
      2
      11 npm
      1
      MIT

    • Claude Team MCP

      7836246
      A
      license
      B
      quality
      C
      maintenance
      Enables collaboration between multiple AI models (GPT, Claude, Gemini) to work together on complex tasks, with intelligent task distribution and role-based expert assignment for code development, review, and optimization.
      18
      7 npm
      49
      MIT

    • llm-router-mcp

      Kijun0708
      A
      license
      D
      quality
      B
      maintenance
      Enables Claude Code as a team leader to delegate tasks to GPT and Gemini experts, supporting multi-LLM collaboration with tools for consultation, code review, design, and background execution.
      76
      9 npm
      MIT

    • PeerBridge MCP

      Hoylon
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects multiple AI agents (Codex, Claude Code, Grok, etc.) into a coordinated, auditable team with shared memory, task ownership, and human oversight, enabling parallel collaboration without conflicts.
      238
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools have distinct purposes but there is some overlap between create_mission, create_project_plan, and send_directive for task creation. Also, ask_question/answer_question are clear pairs. Overall, an agent can distinguish, but minor ambiguity exists.

    Naming Consistency4/5

    Tool names follow a mostly consistent verb_noun pattern in snake_case (e.g., create_mission, get_project_state). However, a few tools like 'ping', 'status', and 'init' lack a noun after the verb, deviating from the pattern.

    Tool Count4/5

    28 tools is slightly high but reasonable for a collaboration server covering missions, projects, tasks, tickets, autonomous loops, and reporting. The scope justifies the count, though some consolidation could help.

    Completeness3/5

    The tools cover core lifecycle operations for projects and tickets but are missing delete operations for missions, tasks, and tickets. Also, no explicit update_task tool exists. This leaves some gaps that agents may need to work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources