Model Context Protocol
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.
Claude Code
Why has our ROTI dropped two sprints in a row?
retro.board.roti.get
Cursor
List every action item still open on the Backend team and who owns it.
retro.actions.list
Claude
Summarise Friday's retrospective for the two people who missed it.
retro.board.summary.get
VS Code
Find every mention of flaky tests across our retrospectives.
retro.boards.search
Claude Code
Open a poker game for the next sprint and import its tasks.
poker.game.tasks.import
Claude
Where does the team disagree most about how things are going?
retro.board.health.get
Claude Code
Why has our ROTI dropped two sprints in a row?
retro.board.roti.get
Cursor
List every action item still open on the Backend team and who owns it.
retro.actions.list
Claude
Summarise Friday's retrospective for the two people who missed it.
retro.board.summary.get
VS Code
Find every mention of flaky tests across our retrospectives.
retro.boards.search
Claude Code
Open a poker game for the next sprint and import its tasks.
poker.game.tasks.import
Claude
Where does the team disagree most about how things are going?
retro.board.health.get
Claude Code
Why has our ROTI dropped two sprints in a row?
retro.board.roti.get
Cursor
List every action item still open on the Backend team and who owns it.
retro.actions.list
Claude
Summarise Friday's retrospective for the two people who missed it.
retro.board.summary.get
VS Code
Find every mention of flaky tests across our retrospectives.
retro.boards.search
Claude Code
Open a poker game for the next sprint and import its tasks.
poker.game.tasks.import
Claude
Where does the team disagree most about how things are going?
retro.board.health.get
Claude Code
Why has our ROTI dropped two sprints in a row?
retro.board.roti.get
Cursor
List every action item still open on the Backend team and who owns it.
retro.actions.list
Claude
Summarise Friday's retrospective for the two people who missed it.
retro.board.summary.get
VS Code
Find every mention of flaky tests across our retrospectives.
retro.boards.search
Claude Code
Open a poker game for the next sprint and import its tasks.
poker.game.tasks.import
Claude
Where does the team disagree most about how things are going?
retro.board.health.get
Claude Code
Approve the follow-ups the board suggested for the urgent themes, and put a name on each.
retro.board.suggested_actions.promote
Cursor
Close the actions we shipped in this release.
retro.actions.complete
Claude
What came out of yesterday's retro as most urgent, and what does it suggest we do?
retro.board.insights.list
VS Code
Draft tomorrow's agenda from what stayed unresolved last retro.
retro.board.actions.list
Claude Code
How many people actually showed up to each of the last six retros?
retro.boards.list
Cursor
Push the estimates we agreed in poker back to Jira.
poker.game.task.sync
Claude Code
Approve the follow-ups the board suggested for the urgent themes, and put a name on each.
retro.board.suggested_actions.promote
Cursor
Close the actions we shipped in this release.
retro.actions.complete
Claude
What came out of yesterday's retro as most urgent, and what does it suggest we do?
retro.board.insights.list
VS Code
Draft tomorrow's agenda from what stayed unresolved last retro.
retro.board.actions.list
Claude Code
How many people actually showed up to each of the last six retros?
retro.boards.list
Cursor
Push the estimates we agreed in poker back to Jira.
poker.game.task.sync
Claude Code
Approve the follow-ups the board suggested for the urgent themes, and put a name on each.
retro.board.suggested_actions.promote
Cursor
Close the actions we shipped in this release.
retro.actions.complete
Claude
What came out of yesterday's retro as most urgent, and what does it suggest we do?
retro.board.insights.list
VS Code
Draft tomorrow's agenda from what stayed unresolved last retro.
retro.board.actions.list
Claude Code
How many people actually showed up to each of the last six retros?
retro.boards.list
Cursor
Push the estimates we agreed in poker back to Jira.
poker.game.task.sync
Claude Code
Approve the follow-ups the board suggested for the urgent themes, and put a name on each.
retro.board.suggested_actions.promote
Cursor
Close the actions we shipped in this release.
retro.actions.complete
Claude
What came out of yesterday's retro as most urgent, and what does it suggest we do?
retro.board.insights.list
VS Code
Draft tomorrow's agenda from what stayed unresolved last retro.
retro.board.actions.list
Claude Code
How many people actually showed up to each of the last six retros?
retro.boards.list
Cursor
Push the estimates we agreed in poker back to Jira.
poker.game.task.sync
Ask in plain language
What teams actually ask it
The server hands your client the same data the app shows — boards, cards, action items, health checks and ROTI — so the question can be about the team instead of about which screen to open.
Find what keeps coming back
Search 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 closed
List 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 time
Pull health checks and ROTI scores sprint by sprint and ask why a trend moved, instead of comparing screenshots by hand.
Prepare a planning poker session
Open 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.
Press play, not sign-up
Pick a job, watch the client do it
Every card below is a real chain of tool calls. Choose one and the terminal replays what your client would print — same tool names, same order, same kind of answer.
~/qretro — claude
✻ Welcome to Claude Code
qretro MCP server connected · 29 tools
cwd: ~/qretro
Press ↵ to run this question on a real retrospective.
>
⏵⏵ accept edits on (shift+tab to cycle)? for shortcuts
Paste both into your own client and you get an answer about your team, not about this one.
One address, any client
Connect the client you already have open
Add mcp.qretro.com as a server and sign in when the client asks. Nothing to paste, nothing to rotate, and access is revoked from Settings whenever you want.
Claude
Settings → Connectors → Add custom connector, then paste the address. Works on web and desktop.
Claude Code
Add the server with one command, then run /mcp in a session — the browser step is handled for you.
Cursor
Add the server by URL in MCP settings. There is no token field to fill; the sign-in page opens on the first request.
VS Code
Same as Cursor — the server URL on its own, and anything else that speaks MCP over HTTP connects this way too.
Where nobody can press Authorize — CI jobs, cron scripts, headless runs — use a scoped API token instead, optionally bound to a single team.
Predictable names
What the client can call
Every tool follows domain.scope.action, so a client that found one can guess the next. Reading needs mcp:read, writing back needs mcp:write.
Retrospectives
Team list
retro.teams.listEvery team you belong to, and how many retrospectives each one has in total.
Team members
retro.team.members.listWho is in the team and what each one is allowed to do — the source of user IDs for assigning work.
Retrospectives list
retro.boards.listA team's retrospectives, newest first — narrowed to a period or to the finished ones.
Search retrospectives
retro.boards.searchKeyword search across summaries, action items and everything participants wrote.
Board messages
retro.board.messages.listEvery card on the board, grouped by column, with its sentiment, category and votes.
Board summary
retro.board.summary.getThe board's summary and the people who took part in it.
Board insights
retro.board.insights.listTopic clusters with sentiment and urgency, each with the follow-up it suggests.
Approve a suggestion
retro.board.suggested_actions.promoteTurn a follow-up the board came up with into an agreement, keeping its wording and the theme it came from.
Dismiss a suggestion
retro.board.suggested_actions.rejectDrop a follow-up the team does not want — nothing lands on the board.
Team health
retro.board.health.getA score per category on a 0–10 scale, plus alignment, turnout and the trend across previous retros.
ROTI score
retro.board.roti.getThe ROTI score with its distribution and how it moved sprint over sprint.
Open action items across retros
retro.actions.listOpen actions across every retrospective at once, with team, board, assignee and overdue flag.
Action items
retro.board.actions.listActions agreed on one board, with status, priority and assignee.
Create action item
retro.actions.createAdd an action to a board without opening it, with a priority and a due date.
Update action item
retro.actions.updateChange what an action says, who owns it, when it is due or how urgent it is.
Complete action item
retro.actions.completeMark an action done once the work has actually landed.
Update message
retro.board.messages.updateCorrect the wording of a card you wrote yourself.
Prompts, not just tools
Analyze a retrospective
/mcp__qretro__analyze-retroWalks one board end to end — summary, clusters, agreements, health, ROTI — and reports themes, risks and what to do next.
Team health over time
/mcp__qretro__team-healthCompares the team's last retrospectives: where health and ROTI are heading, how many agreements actually get closed, what keeps repeating.
You do not type those names. Press / in Claude Code and the server's prompts sit in the list next to the built-in commands — pick one and it runs. The long form is just how the client identifies them: the mcp__ prefix, the name you gave the server, the name of the prompt.
Planning poker
Connected trackers
poker.sources.listWhich trackers the team connected and what each one can do — search, sprints, writing estimates back.
Find a sprint
poker.iterations.listActive and upcoming sprints from the connected tracker, ready to estimate.
Open a poker game
poker.games.createOpen a game and get the link participants join with.
Import sprint tasks
poker.game.tasks.importPull a whole sprint into the game, or just the tasks a search turns up.
Sync estimates
poker.game.task.syncWrite the agreed estimate back to the task in the tracker.
Connect in about a minute
Point your client at mcp.qretro.com, approve the permissions once, and your retrospectives are part of the session.
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.
