Your retrospectives, available to any MCP client
QRetro runs a Model Context Protocol server, so Claude, Claude Code, Cursor, VS Code and anything else that speaks MCP can read your boards, health trends and open action items — and write back. Connect with one address and a sign-in, or with a scoped API token for automations.
What teams actually ask it
Find what keeps coming backSearch across every retrospective the team has run and get the themes that repeat — the ones nobody notices because each session only shows one sprint at a time.
Chase the action items nobody closedList every open action across boards, see how long each has been open, and mark the finished ones complete without leaving your editor.
Track health and ROTI over timePull health checks and ROTI scores sprint by sprint and ask why a trend moved, instead of comparing screenshots by hand.
Prepare a planning poker sessionOpen a game, import the sprint's tasks from Jira or Linear, and sync agreed estimates back to the tracker — all from the client you already have open.
Sign in, no tokens
Connect your favorite MCP client
Give the client one address — mcp.qretro.com — sign in to QRetro, and analyze boards, get summaries, and extract action items from there. Works with Claude, Claude Code, Cursor, VS Code, and anything else that speaks the Model Context Protocol.
- One address, nothing to paste
The client brings you to QRetro, shows the permissions it asks for, and renews access on its own. Revoke it any time in Settings. - Bring your own model
Claude Opus 5, GPT-5.6 Sol, Gemini 3.1 Pro, Grok 4.5 — your board data goes to whichever model your client runs. - Deep analytics
Analyze team health (ROTI) and sprint-over-sprint trends with automated contextual reports. - Auto Action extraction
Let the system handle the routine work. It compiles Agreed Actions from the team's discussion automatically.
Available tools
Team listretro.teams.list
Retrospectives listretro.boards.list
Open action items across retrosretro.actions.list
Board messagesretro.board.messages.list
Board summaryretro.board.summary.get
Action itemsretro.board.actions.list
Board insightsretro.board.insights.list
Team healthretro.board.health.get
ROTI scoreretro.board.roti.get
Search retrospectivesretro.boards.search
Create action itemretro.actions.create
Update action itemretro.actions.update
Complete action itemretro.actions.complete
Update messageretro.board.messages.update
Find a sprintpoker.iterations.list
Open a poker gamepoker.games.create
Import sprint taskspoker.game.tasks.import
Sync estimatespoker.game.task.sync
~/qretro — claude
✻ Welcome to Claude Code
qretro MCP server connected · 15 tools
cwd: ~/qretro
Press ↵ to run this question on a real retrospective.
>
⏵⏵ accept edits on (shift+tab to cycle)? for shortcuts
Frequently asked questions
https://mcp.qretro.com. Give that address to your client and it will bring you to QRetro to sign in — there is nothing to paste and no token to manage.
Anything that implements the Model Context Protocol over HTTP. Claude on web and desktop, Claude Code, Cursor and VS Code are the ones teams use most; other clients connect the same way by adding the server URL.
Only when nobody can press Authorize in a browser — CI jobs, cron scripts and headless agent runs — or when the access needs to be narrower than a sign-in gives. A signed-in connection covers every team you belong to; a token can be bound to a single team and is the only way to grant message deletion.
Whichever model your client runs. The MCP server hands data to the client, and the client decides where it goes — QRetro does not send your boards to a model of its own.
In Settings under API Keys. Sign-in connections are listed as connected applications and can be revoked individually; API tokens are revoked from the same screen.
