Skip to main content
Glama

Related Servers

Alternatives to Claude Team MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to orchestrate multiple models from different providers within a single conversation, supporting collaborative code review, planning, debugging, and implementation workflows with full context continuity.
      -
    • 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
      16 npm
      MIT
    • 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.
      241
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables multi-agent AI collaboration by connecting Claude Code, OpenAI Codex, and Google Antigravity, providing cross-model code reviews, independent second opinions, and autonomous validation through MCP tools.
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI agents like Claude and Codex to coordinate on the same project through shared tasks, file locks, and a real-time dashboard, preventing conflicts and streamlining collaborative development.
      8 npm
      1
      MIT

    TDQS

    B3/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have distinct purposes (e.g., analyze_project_structure vs. team_work), but some overlap exists between 'ask_expert', 'code_review', and 'fix_bug' as they all involve expert interaction, though at different stages of development.

    Naming Consistency4/5

    Tools predominantly use snake_case with descriptive names (e.g., 'analyze_project_structure', 'generate_commit_message'), but some like 'history_context' and 'team_dashboard' are more noun-centric, breaking the verb_noun pattern slightly.

    Tool Count4/5

    At 18 tools, the server is slightly above the ideal range of 3-15 but still manageable. The count aligns with the broad scope of team collaboration, workflow management, and history tracking.

    Completeness4/5

    The tool set covers key operations for team collaboration (analysis, code review, bug fixing, workflow execution, history) but lacks administrative features like workflow creation or team member management, leaving minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues