Skip to main content
Glama
Sign In
7836246

Claude Team MCP

by 7836246
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Claude Team MCP

No user-submitted related servers found.

    Related Servers

    • PAL MCP

      crowx01
      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.
      -

    • llm-router-mcp

      Kijun0708
      A
      license
      D
      quality
      C
      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
      24 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.
      241
      Apache 2.0

    • @h0wzy/mcp

      H0wZy
      A
      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
      MIT
    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/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

    Resources