Release notes
MCP and external automation access to retrospective data
QRetro has become part of the team's workflow: added MCP, access keys, and tools for external automations and assistants.
Last updated
March 6, 2026
QRetro can now be connected to external automations and assistants as a structured source of retrospective context.
2026
Deeper integrations and context from work systems
Expanded the integration layer so the team comes to the retro not with a blank slate, but with live context from Jira and Linear.
Deepened the connection between team health and post-retro follow-ups
Strengthened the final stage of the retrospective to make it easier for the team to transition from discussion to tasks and see the team's overall state.
Retro preparation is now asynchronous thanks to Draft mode
Added draft boards to gather thoughts and signals prior to the meeting, rather than spending all the call time on initial context gathering.
System analytics for team health and ROTI are now available
QRetro now helps not only to run retrospectives but also to track team health dynamics and the usefulness of the meetings themselves.
The system now prepares retro summaries and recommended next steps
Added automatic summaries, recommended next steps, and a new analytical layer on top of team discussions.
Simplified product entry for meeting participants
Reduced entry friction: shadow users, magic links, and OTP make joining retros faster and easier.
Retro summaries, board visibility, and sharing are now a fully-fledged part of the product
Enhanced retrospective closure: meeting summaries, a timer, public visibility, and convenient result sharing.
Retrospectives are now more lively: grouping, reactions, and a new workflow
Enhanced board collaboration to keep discussions in large retrospectives organized and manageable.
