retro-bot vs Data-grounded sprint retro
retro-bot is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑28.
retro-bot is a plugin bundle for AI coding tools published by CR8-OS. No marketplace we read lists it any more. Data-grounded sprint retro is an MCP server published by sathvic-kollu. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Data-grounded sprint retro | |
|---|---|---|
| Community marketplace cometogather/retro-bot | Removed on 2026-10-28 Version: 1.3.0 Forks (GitHub): 0 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Downloads/month (npm): 136 Downloads/week (npm): 57 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | retro-botno longer listed · | Data-grounded sprint retro |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 14 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (retro-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 9, secrets among them: 3 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cr8-os/retro-bot | github.com/sathvic-kollu/retro-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of retro-bot
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
LLM-driven session retrospection. Detects friction in agent sessions (mechanical pre-pass + LLM inference + cross-session) and materializes approved learnings into user memory…
-
Stay on top of your product — briefings, meeting processing, stakeholder comms
-
slim-meeting-agenda
Generate comprehensive meeting agendas by orchestrating context gathering from previous summaries, querying external services (GitHub, Slack, etc. via TECH.md), and matching…
-
Flow turns Claude into a project partner who manages your backlog. Say "park this for later," and it queues the idea. Say "what's next?" and it finds the highest-priority ready…
-
Transform brain dumps into implementation specs through an evidence-gated interview stress-tested by adversarial plan critics. Interactive HTML contract for planning decisions…
-
Run structured multi-agent decision reviews with Codex, Claude Code, and adapter-based CLI agents.
What each says it does
retro-bot
An agile retrospective skill for your Claude collaboration sessions. Capture what you learned. Apply the fix. Make the next session better.
Data-grounded sprint retro
Data-grounded sprint retrospectives from your Jira, GitHub, and Slack activity.
How to run each
retro-bot
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Data-grounded sprint retro As a local MCP server: npm package
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --env "JIRA_API_TOKEN=<YOUR_JIRA_API_TOKEN>" --env "SLACK_TOKEN=<YOUR_SLACK_TOKEN>" --transport stdio retro-mcp -- npx -y retro-mcpRequires: GITHUB_TOKEN (secret), JIRA_API_TOKEN (secret), SLACK_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of retro-bot publish no settings it asks for, so we do not compare settings.
What it can do: retro-bot · What it can do: Data-grounded sprint retro · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.