TeamRetro MCP Server

What does “TeamRetro” MCP Server do?

The TeamRetro MCP Server is a Model Context Protocol (MCP) server designed to integrate AI assistants with the TeamRetro platform. It acts as a bridge between AI clients and TeamRetro’s official API, enabling seamless access to team management, retrospectives, health checks, and other collaboration features. By exposing over 20 standardized MCP tools, the server allows developers to automate tasks such as managing teams, users, and actions, as well as retrieving analytical insights. The TeamRetro MCP Server supports secure API authentication and offers built-in pagination and filtering for efficient data handling. This enables AI applications to easily incorporate TeamRetro functionality into workflows, improving productivity and empowering AI-driven team analytics and management.

List of Prompts

No prompt templates are mentioned in the available documentation or repository files.

List of Resources

No explicit resources are listed or described in the available documentation or repository files.

List of Tools

• The README indicates the server exposes 20+ tools for managing teams, users, actions, and more, but no explicit names or details for these tools are found in the visible documentation or files.*

Use Cases of this MCP Server

• AI-powered team analytics
  Leverage TeamRetro data for automated insights and reporting to support data-driven decision-making for team health and performance.

• Automated retrospective management
  Use AI to schedule, run, and summarize retrospectives, reducing manual overhead and ensuring actionable outcomes.

• Integration into custom AI workflows
  Seamlessly connect TeamRetro features to other AI-driven tools or dashboards, streamlining team management processes.

• Health check automation
  Automatically trigger and analyze health checks, providing real-time team sentiment and engagement data for leaders.

• Efficient team/user management
  Simplify the creation, deletion, and modification of teams and users from an AI interface, improving administrative efficiency.

How to set it up

Windsurf

1. Ensure Node.js and npm are installed on your system.

2. Locate your Windsurf configuration file (e.g., windsurf.config.json).

3. Add the TeamRetro MCP Server to the mcpServers section:

   {
     "mcpServers": {
       "teamretro-mcp": {
         "command": "npx",
         "args": ["@teamretro/mcp-server@latest"]
       }
     }
   }
   

4. Save the configuration and restart Windsurf.

5. Verify the MCP server is running and accessible in your platform.

Securing API Keys

Set your TeamRetro API key using environment variables. Example:

{
  "mcpServers": {
    "teamretro-mcp": {
      "command": "npx",
      "args": ["@teamretro/mcp-server@latest"],
      "env": {
        "TEAMRETRO_API_KEY": "your-teamretro-api-key"
      }
    }
  }
}

Claude

1. Install Node.js and npm, if not already present.

2. Open Claude’s configuration file.

3. Add the TeamRetro MCP Server as follows:

   {
     "mcpServers": {
       "teamretro-mcp": {
         "command": "npx",
         "args": ["@teamretro/mcp-server@latest"]
       }
     }
   }
   

4. Restart Claude to load the new MCP server.

5. Confirm setup by checking the MCP connections in Claude.

Cursor

1. Make sure Node.js and npm are available.

2. Edit your Cursor settings.json (or platform-specific config).

3. Include the TeamRetro MCP Server:

   {
     "mcpServers": {
       "teamretro-mcp": {
         "command": "npx",
         "args": ["@teamretro/mcp-server@latest"]
       }
     }
   }
   

4. Save changes and restart Cursor.

5. Check the MCP integration status for confirmation.

Cline

1. Install Node.js and npm.

2. Open Cline’s MCP configuration file.

3. Add the following entry:

   {
     "mcpServers": {
       "teamretro-mcp": {
         "command": "npx",
         "args": ["@teamretro/mcp-server@latest"]
       }
     }
   }
   

4. Save and restart Cline.

5. Validate that the TeamRetro MCP Server is operational.

Securing API Keys

Always use environment variables to manage sensitive credentials. Example:

{
  "mcpServers": {
    "teamretro-mcp": {
      "command": "npx",
      "args": ["@teamretro/mcp-server@latest"],
      "env": {
        "TEAMRETRO_API_KEY": "your-teamretro-api-key"
      }
    }
  }
}

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "teamretro-mcp": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “teamretro-mcp” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.

Overview

Based on the provided documentation, the TeamRetro MCP Server provides strong overview and setup guidance, but lacks public documentation for its prompt templates, explicit resources, and tool specifics. It supports secure API key management via environment variables, but there is no mention of Roots or sampling support. The project is open source and licensed under Apache-2.0.

Our opinion

This MCP server has solid documentation for setup and integration, and a reputable open-source license. However, the absence of detailed tool, prompt, and resource documentation lowers its score for immediate usability and discoverability. If the missing documentation is addressed, it would greatly improve both user experience and developer integration.

MCP Score