TeamRetro MCP Server

by adepanges
Verified

remote-capable server

The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.

TeamRetro MCP Server

Model Context Protocol (MCP) server for TeamRetro integration.

Important Notes

Unofficial MCP Server

This MCP server is an unofficial community-developed interface to TeamRetro's services. While not developed or endorsed by TeamRetro, it provides standardized access to their platform.

Official API Integration

The server connects directly to TeamRetro's official public API:

  • Uses documented endpoints from TeamRetro's API specifications
  • Maintains full API compliance and version tracking
  • Implements all required authentication methods
  • Preserves original API responses without modification

API Documentation Source

All API endpoints and functionality are based on TeamRetro's official documentation:

Available Tools

For a complete list of available MCP tools and their usage, see TOOLS.md.

Changelog

For a detailed list of changes and updates, see CHANGELOG.md.

How to Use

{ "mcpServers": { "teamretro-mcp-server": { "command": "npx", "args": ["-y", "teamretro-mcp-server"], "env": { "TEAMRETRO_BASE_URL": "https://api.teamretro.com", "TEAMRETRO_AUTH_TYPE": "apiKey", "TEAMRETRO_API_KEY": "your-api-key" } } } }

From Source Code

  1. Clone the repository, install dependencies, and build the project:
git clone https://github.com/adepanges/teamretro-mcp-server.git cd teamretro-mcp-server npm install npm run build

Running in AI Client

  1. Configure the AI client with the following settings:
{ "mcpServers": { "teamretro-mcp-server": { "command": "node", "args": ["/path/to/teamretro-mcp-server/dist/index.js"], "env": { "TEAMRETRO_BASE_URL": "https://api.teamretro.com", "TEAMRETRO_AUTH_TYPE": "apiKey", "TEAMRETRO_API_KEY": "your-api-key" } } } }

Running with Inspector

  1. Configure the environment variables by copying .env.example to .env and modifying it according to your needs.
  2. Run the server with inspector:
npm run inspector

Environment Variables Examples

API Key Authentication (Default)

{ "env": { "TEAMRETRO_BASE_URL": "https://api.teamretro.com", "TEAMRETRO_AUTH_TYPE": "apiKey", "TEAMRETRO_API_KEY": "your-api-key" } }

Basic Authentication

{ "env": { "TEAMRETRO_BASE_URL": "https://api.teamretro.com", "TEAMRETRO_AUTH_TYPE": "basic", "TEAMRETRO_USERNAME": "your-username", "TEAMRETRO_PASSWORD": "your-password" } }

Bearer Token Authentication

{ "env": { "TEAMRETRO_BASE_URL": "https://api.teamretro.com", "TEAMRETRO_AUTH_TYPE": "bearer", "TEAMRETRO_TOKEN": "your-bearer-token" } }

Logging Configuration

{ "env": { "TEAMRETRO_LOG_ENABLED": true, "TEAMRETRO_LOG_DIR": "/your-directory/logs", "TEAMRETRO_LOG_LEVEL": "info", "TEAMRETRO_LOG_MAX_FILES": 30 } }

You must be authenticated.

A
security – no known vulnerabilities
A
license - permissive license
A
quality - confirmed to work

MCP server for TeamRetro integration. Provides standardized access to TeamRetro's official API with support for API key, basic auth, and bearer token authentication. Strictly follows TeamRetro's API specifications while maintaining full compliance. Includes tools for managing retrospectives, teams, actions, and health checks.

  1. Important Notes
    1. Unofficial MCP Server
    2. Official API Integration
    3. API Documentation Source
  2. Available Tools
    1. Changelog
      1. How to Use
        1. NPX (Recommended, Easy Setup)
        2. From Source Code
        3. Environment Variables Examples
      ID: v70elvd74e