Data-grounded sprint retro MCP Server

What the code does

We read the source, 19 h ago · rules 3dff92dd89df

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

retro-mcp похож на metro-mcp

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add retro-mcp -- npx -y retro-mcp

{
  "mcpServers": {
    "retro-mcp": {
      "args": [
        "-y",
        "retro-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.retro-mcp]
command = "npx"
args = ["-y", "retro-mcp"]

{
  "mcpServers": {
    "retro-mcp": {
      "args": [
        "-y",
        "retro-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "retro-mcp": {
      "args": [
        "-y",
        "retro-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: JIRA_BASE_URL (Your Jira Cloud site, e.g. https://your-company.atlassian.net. Required for a live retro.), JIRA_EMAIL (Atlassian account email the API token belongs to.), JIRA_API_TOKEN (Jira API token from id.atlassian.com. Read-only use.), JIRA_BOARD_ID (Optional board id to pin when the account has several boards.), GITHUB_TOKEN (Optional GitHub read-only token for PR review latency and reverts.), GITHUB_REPOS (Optional comma-separated owner/name repos to scope PR analysis.), SLACK_TOKEN (Optional Slack read token to scan sprint channels for blocker and incident language.), SLACK_CHANNELS (Optional comma-separated Slack channel ids to scan for the sprint window.), RETRO_DEMO_MODE (Set to true to force the synthetic demo sprint even when credentials are present.). The author declared them in the registry entry; get the values from the project itself.