Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Data-grounded sprint retro

by sathvic-kolluversion 0.1.0i★ 0iRuns on your computerRepository ↗
Registry nameio.github.sathvic-kollu/retro-mcp

How to install

What it does

Data-grounded sprint retrospectives from your Jira, GitHub, and Slack activity.

  • Connects Runs on your computer
  • Account or key Needs JIRA_API_TOKEN · 1 setting to fill in (JIRA_BASE_URL)
  • Category Developer tools

Use together with

Skills that teach the AI this kind of work; they work alongside this one

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

by morluto★ 468,7331 skills

Skill · How-to guide

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

by multica-ai★ 234,3321 skills

Skill · How-to guideNo license stated

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

by Graphify-Labs★ 150,2871 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness3/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score3/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Data-grounded sprint retro. Follow https://mcp.popnx.com/i/sathvic-kollu-retro-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a Data-grounded sprint retro key (create it on the maker’s site) · 1 setting(s) to fill in (JIRA_BASE_URL) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Data-grounded sprint retro for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "retro": { "command": "npx", "args": [ "-y", "retro-mcp" ], "env": { "JIRA_BASE_URL": "your-value", "JIRA_API_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For JIRA_API_TOKEN, JIRA_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Data-grounded sprint retro tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Data-grounded sprint retro key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Data-grounded sprint retro site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • JIRA_BASE_URL Your Jira Cloud site, e.g. https://your-company.atlassian.net. Required for a live retro.

    Descriptions are as written by the maker.

  4. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  5. Paste these settings and save the file

    {
      "mcpServers": {
        "retro": {
          "command": "npx",
          "args": [
            "-y",
            "retro-mcp"
          ],
          "env": {
            "JIRA_BASE_URL": "your-value",
            "JIRA_API_TOKEN": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Quit Claude and open it again

  7. Try it

    Use Data-grounded sprint retro and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Data-grounded sprint retro or shows a Data-grounded sprint retro tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • JIRA_EMAIL Atlassian account email the API token belongs to.
  • 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.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Data-grounded sprint retro yet

Data-grounded sprint retro runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Data-grounded sprint retro

  • You need a Data-grounded sprint retro key (create it on the maker’s site) · 1 setting(s) to fill in (JIRA_BASE_URL) · Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a Data-grounded sprint retro key (create it on the maker’s site) · 1 setting(s) to fill in (JIRA_BASE_URL) · Install Node.js on your computer first (one time)
  • You need a Data-grounded sprint retro key (create it on the maker’s site) · 1 setting(s) to fill in (JIRA_BASE_URL) · Install Node.js on your computer first (one time)
  • You need a Data-grounded sprint retro key (create it on the maker’s site) · 1 setting(s) to fill in (JIRA_BASE_URL) · Install Node.js on your computer first (one time)

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a Data-grounded sprint retro key (create it on the maker’s site) · 1 setting(s) to fill in (JIRA_BASE_URL) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Data-grounded sprint retro for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user retro --env JIRA_BASE_URL=your-value --env JIRA_API_TOKEN=your-value -- npx -y retro-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For JIRA_API_TOKEN, JIRA_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Data-grounded sprint retro tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Data-grounded sprint retro key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Data-grounded sprint retro site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • JIRA_BASE_URL Your Jira Cloud site, e.g. https://your-company.atlassian.net. Required for a live retro.

    Descriptions are as written by the maker.

  4. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  5. Paste this command and press Enter

    claude mcp add --scope user retro --env JIRA_BASE_URL=your-value --env JIRA_API_TOKEN=your-value -- npx -y retro-mcp

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Type /mcp in Claude Code

    You should see Data-grounded sprint retro listed as connected

  7. Try it

    Use Data-grounded sprint retro and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Data-grounded sprint retro or shows a Data-grounded sprint retro tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • JIRA_EMAIL Atlassian account email the API token belongs to.
  • 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.

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a Data-grounded sprint retro key (create it on the maker’s site) · 1 setting(s) to fill in (JIRA_BASE_URL) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Data-grounded sprint retro for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "retro": { "command": "npx", "args": [ "-y", "retro-mcp" ], "env": { "JIRA_BASE_URL": "your-value", "JIRA_API_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For JIRA_API_TOKEN, JIRA_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Data-grounded sprint retro tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Data-grounded sprint retro key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Data-grounded sprint retro site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • JIRA_BASE_URL Your Jira Cloud site, e.g. https://your-company.atlassian.net. Required for a live retro.

    Descriptions are as written by the maker.

  4. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  5. Fill in your key

    In the Data-grounded sprint retro settings, JIRA_API_TOKEN, JIRA_BASE_URL is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in Cursor in Agent mode

  7. Try it

    Use Data-grounded sprint retro and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Data-grounded sprint retro or shows a Data-grounded sprint retro tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • JIRA_EMAIL Atlassian account email the API token belongs to.
  • 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.

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a Data-grounded sprint retro key (create it on the maker’s site) · 1 setting(s) to fill in (JIRA_BASE_URL) · Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Data-grounded sprint retro for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "retro": { "type": "stdio", "command": "npx", "args": [ "-y", "retro-mcp" ], "env": { "JIRA_BASE_URL": "your-value", "JIRA_API_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For JIRA_API_TOKEN, JIRA_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Data-grounded sprint retro tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Sign up and create a Data-grounded sprint retro key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    Open the Data-grounded sprint retro site ↗

  3. Fill in 1 setting(s)

    These are program settings, not keys. No sign-up needed; fill them in as the maker describes.

    • JIRA_BASE_URL Your Jira Cloud site, e.g. https://your-company.atlassian.net. Required for a live retro.

    Descriptions are as written by the maker.

  4. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  5. Fill in your key

    In the Data-grounded sprint retro settings, JIRA_API_TOKEN, JIRA_BASE_URL is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  6. Open the AI chat in VS Code in Agent mode

  7. Try it

    Use Data-grounded sprint retro and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Data-grounded sprint retro or shows a Data-grounded sprint retro tool in the answer, you are connected

7 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • JIRA_EMAIL Atlassian account email the API token belongs to.
  • 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.

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Data-grounded sprint retro💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user retro --env JIRA_BASE_URL=your-value --env JIRA_API_TOKEN=your-value -- npx -y retro-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "retro": {
      "command": "npx",
      "args": [
        "-y",
        "retro-mcp"
      ],
      "env": {
        "JIRA_BASE_URL": "your-value",
        "JIRA_API_TOKEN": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "retro": {
      "command": "npx",
      "args": [
        "-y",
        "retro-mcp"
      ],
      "env": {
        "JIRA_BASE_URL": "your-value",
        "JIRA_API_TOKEN": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "retro": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "retro-mcp"
      ],
      "env": {
        "JIRA_BASE_URL": "your-value",
        "JIRA_API_TOKEN": "your-value"
      }
    }
  }
}

Values you fill in

  • JIRA_BASE_URL required env
    Your Jira Cloud site, e.g. https://your-company.atlassian.net. Required for a live retro.
  • JIRA_EMAIL env
    Atlassian account email the API token belongs to.
  • JIRA_API_TOKEN secret required env
    Jira API token from id.atlassian.com. Read-only use.
  • JIRA_BOARD_ID env
    Optional board id to pin when the account has several boards.
  • GITHUB_TOKEN secret env
    Optional GitHub read-only token for PR review latency and reverts.
  • GITHUB_REPOS env
    Optional comma-separated owner/name repos to scope PR analysis.
  • SLACK_TOKEN secret env
    Optional Slack read token to scan sprint channels for blocker and incident language.
  • SLACK_CHANNELS env
    Optional comma-separated Slack channel ids to scan for the sprint window.
  • RETRO_DEMO_MODE env
    Set to true to force the synthetic demo sprint even when credentials are present.

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
50/wk
Connection
Runs on your computer
Latest versioni
0.1.0
Published to registryi
Jun 17, 2026
Code last changedi
Jun 17, 2026
Maker
sathvic-kollu
Packages
npm: retro-mcp
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account sathvic-kollu, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 5 months ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for retro-mcp@0.1.0

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/sathvic-kollu-retro-mcp.svg)](https://mcp.popnx.com/en/servers/sathvic-kollu-retro-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Developer toolsi

  • More stars than 0% of the other 6182 servers in this category
  • Published to the registry more recently than 16% of the other 6182 servers in this category
  • Basic checks equal to or better than 99% of the other 6182 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Data-grounded sprint retro safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: JIRA_API_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 5 months ago, and the latest version (0.1.0) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

by ahmedkhaleel2004Widely used★ 19KUpdated 2 months ago

Runs in the cloud✓ service owner · gitdiagram.comTried by the PopNx team

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

by AppllamaWidely used★ 5.2KUpdated 3 months ago

Runs in the cloud✓ service owner · appllama.io

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

by repowise-devWidely used↓ 6.5K/wk★ 8.2K Stars for the whole repoUpdated 6 days ago

Computer or cloud✓ service owner · repowise.dev
Compared with similar ones
This one
Data-grounded sprint retro
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computer
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoYesNoNo
Basic checks3/34/44/44/44/45/5
LicenseMITMITMITApache-2.0Apache-2.0AGPL-3.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

retro-mcp

A sprint retrospective grounded in what actually happened, not what people remember.

Retros run on memory, so they run on bias. The loudest voice and the last few days win, the same complaints come back every sprint, and the action items quietly never happen. Meanwhile the actual record of the sprint, the reopened ticket, the PR that sat two days in review, the Slack thread where someone said they were blocked, is sitting right there in your tools, unused.

retro-mcp reads that record and hands you a retro built from it. You ask your AI assistant for the retro and it answers with what went well, what didn't, and action items, every line backed by a specific metric, ticket, PR, or thread. It frames everything around the process, never individuals, and it flags the problems that keep recurring across sprints.

It is a standard Model Context Protocol server, so it works in any MCP client (Claude, Cursor, Cline, and more) on any model. It is local and read-only: nothing about your sprint leaves your machine except the calls to your own tools' APIs, and it needs no AI API key. That is also the answer to the obvious worry: it is a retro aid, not a surveillance tool.

See it in 30 seconds (no accounts needed)

It ships with a realistic closed sprint and runs against it automatically when no credentials are set:

npx -y retro-mcp --demo

Here is the headline tool on that demo sprint:

# Sprint Retrospective: MBANK Sprint 23

_May 27 to Jun 10. Demo data, no credentials configured._ _Grounded in 8 issues, 5 merged PRs, and 4 flagged threads. System-level and blameless: this is about the process, not people._

What went well

  • Work moved through faster than last sprint. avg cycle time 4.6d, down from 5.6d.

What did not go well

  • The sprint fell short of its commitment. only 23 of 34 pts done (68%). ⟳ recurring across recent sprints
  • Scope grew mid-sprint. +5 pts across 2 issues pulled in after the sprint started. ⟳ recurring across recent sprints
  • Work carried over into the next sprint. 3 issues (16 pts) not finished. ⟳ recurring across recent sprints
  • Some work was called done before it was. MBANK-203 · reopened 1 time: Statement PDF export.
  • Code review was a bottleneck. PRs waited 20.3h on average for a first review; PR #503 · sat 52h: statement PDF export.
  • Changes had to be reverted or hotfixed. PR #504 · revert: OTP delivery change; 1 hotfix merged.
  • The team hit repeated blockers and interruptions. 2 threads mentioned being blocked; 1 thread mentioned an incident.

Action items

  • (recurring) Adopt a scope-change rule: anything pulled in mid-sprint bumps something out, decided at standup, not silently.
  • (recurring) Pull less or split large items so they finish inside the sprint.
  • Tighten the definition of done: an explicit QA check before anything moves to Done.
  • Add a pre-merge guard on risky changes: a second approval or a smoke test before merge.

Discussion prompts

  • MBANK-203 was reopened once. What made it hard to call done the first time?
  • +5 pts came in after the sprint started. What drove the mid-sprint adds?
  • PR #504 had to be reverted. What would have surfaced the problem before it merged?

Every line points at something real. Nobody typed it from memory, and the three recurring problems are flagged as patterns, not fresh complaints.

What it does

Six tools. Everything defaults to the most recently closed sprint.

ToolWhat you get
retro_briefThe full retro: went well / didn't / action items / discussion prompts, every line evidence-backed, recurring themes flagged.
retro_metricsThe evidence base: completion, mid-sprint scope change, carryover, reopens, cycle time vs prior, velocity, PR review latency, reverts, flagged threads.
action_item_reviewPaste last retro's action items; it attaches this sprint's data to each, so you see what actually moved.
discussion_promptsOpen questions for the board, each grounded in a real anomaly. Questions, not verdicts.
sprint_compareThis sprint vs the prior one, plus the problem themes recurring across recent sprints.
list_sourcesWhich sources are wired, or that you are on demo data.
Why this is different

Every other retro tool is a digital sticky-note board: humans still type the observations from memory, and the "AI" ones just cluster the notes people already wrote. retro-mcp derives the observations from the data itself, across Jira, GitHub, and Slack at once. Specifically:

  • Every finding is grounded. No platitudes. If it cannot cite a metric, ticket, PR, or thread, it does not say it.
  • Blameless by construction. Findings are about the system and the process. It never names or ranks a person.
  • It closes the action-item loop. Teams implement a small fraction of their retro actions, and reviewing the previous ones is the single proven lever. action_item_review puts last retro's items next to this sprint's data.
  • It catches patterns, not just this sprint. Themes that recur across recent sprints are flagged, so "the same complaint every sprint" finally shows up with evidence.
  • It augments the human retro. It outputs prompts for the board, not verdicts that end the conversation.

Example: action_item_review

# Last retro's action items, against this sprint's data

_Demo data. Evidence only. You decide what counts as done._

  • Speed up PR reviews so nothing sits more than a day
  • avg PR review latency this sprint: 20.3h
  • slowest review: PR #503 at 52h
  • Stop pulling unplanned work into the sprint mid-flight
  • scope added mid-sprint: +5 pts (2 issues)
  • completion: 68%
  • Finish what we commit to and cut the carryover
  • carryover this sprint: 3 issues (16 pts)

It does not declare done or not done. It surfaces the evidence and lets the team judge, which keeps it honest.

Privacy

  • Local. It runs on your machine, inside your AI client. There is no retro-mcp server or account.
  • Read-only. Every token it asks for is used only to read. It never writes, posts, or moves anything.
  • No AI key, no third party. It makes no LLM calls of its own. Your sprint data goes only to your tools' APIs and your existing AI client's model.
  • A retro aid, not surveillance. It reports on the system to help the team improve, not on individuals to rank them.

Connect your data

Jira is the spine of a retro, so live mode needs it. GitHub and Slack are optional enrichment, scoped to the closed sprint's dates.

VariableSourceNotes
JIRA_BASE_URL JIRA_EMAIL JIRA_API_TOKENJiraRequired for live. Cloud site, account email, and an API token.
JIRA_BOARD_IDJiraOptional. Pin a board when the account has several.
GITHUB_TOKEN GITHUB_REPOSGitHubOptional. Read-only token and the team's repos (owner/name, comma-separated) for PR review latency and reverts.
SLACK_TOKEN SLACK_CHANNELSSlackOptional. Read token and the sprint channel ids (comma-separated) to scan for blocker and incident language.

Verify before wiring it into a client:

JIRA_BASE_URL=https://you.atlassian.net JIRA_EMAIL=you@co.com JIRA_API_TOKEN=xxx npx -y retro-mcp --check

Connect your AI client

Claude Desktop

Add this to claude_desktop_config.json (Settings, Developer, Edit Config), then restart:

{

"mcpServers": { "retro": { "command": "npx", "args": ["-y", "retro-mcp"], "env": { "JIRA_BASE_URL": "https://your-company.atlassian.net", "JIRA_EMAIL": "you@company.com", "JIRA_API_TOKEN": "your-jira-token", "GITHUB_TOKEN": "ghp_your_token", "GITHUB_REPOS": "your-org/your-app", "SLACK_TOKEN": "[PopNx MCP ตัดค่าที่หน้าตาเหมือนกุญแจออก]", "SLACK_CHANNELS": "C0123ENG" } } } }

Leave the env block out to run on demo data first. Include only the sources you use. Cursor, Cline, Continue, Zed, and Windsurf read the same mcpServers JSON.

How it works

  • Jira is the spine, GitHub and Slack enrich. One provider fans out to whichever sources are configured and tolerates any of them failing, so a misconfigured Slack token never sinks the retro.
  • Metrics come from the changelog. Completion, scope change, carryover, reopens, and cycle time are reconstructed by reading each issue's history, so they reflect what happened, not just the final state.
  • Pure-function engine. Metrics, themes, findings, and the brief are pure functions over normalized data. They run identically on demo and live data, and the tests run them directly.
  • No model in the server. It assembles a factual, evidence-linked retro; your AI client phrases it. That is why it needs no AI key and why it never invents a finding.
src/

index.ts MCP server, stdio transport, --demo/--check/--help config.ts env resolution, demo-mode detection gather.ts one place that pulls the sprint, PRs, and signals together provider.ts aggregator over Jira + GitHub + Slack types.ts normalized domain types and source interfaces jira/normalize.ts raw Jira to normalized, plus the ADF flattener sources/ jira, github, slack clients, plus the demo provider analytics/ metrics, themes, findings, actionReview, prompts, brief tools/ one MCP tool per file, thin wrappers over analytics

What has been verified

  • All six tools run end to end over real MCP stdio (npm test).
  • The Jira parse layer is unit tested against a documented Cloud payload (test/normalize.test.ts).
  • The retro engine is unit tested: changelog-derived metrics, recurring-theme detection across sprints, and evidence-grounded findings (test/retro.test.ts).
  • The whole engine is exercised against the demo sprint and reconciles across tools (npm run smoke).

The demo proves the engine. It does not prove each live client against every account shape, which is why the parse layer is unit tested separately and each source is kept small and tolerant. Run --check to confirm your own connections.

Roadmap

  • Linear cycles as an alternative sprint spine
  • A persisted action-item ledger so the loop closes automatically, no pasting
  • Status-dwell and cumulative-flow detail for cycle-time bottlenecks
  • GitLab and Bitbucket
  • A one-call "retro pack" that bundles the brief, metrics, and prompts for the facilitator

Built by Sathvic Kollu

I run delivery for SaaS and fintech teams, and I build tools like this with Claude Code. This is the third in a set of PM-focused MCP servers, after jira-pm-mcp and standup-mcp. If it makes your retro sharper, I would like to hear how you use it.

Issues and pull requests are welcome.

License

MIT. See LICENSE.