Data-grounded sprint retro MCP Server

Data-grounded sprint retro is an MCP integration. Data-grounded sprint retrospectives from your Jira, GitHub, and Slack activity.

Packages and local setup

The published npm package is retro-mcp, version 0.1.0. Its declared MCP transport is stdio.

The package declares 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.