# com.qretro/retro

- Registry name: `com.qretro/retro` · version 1.3.0
- Categories (automatic, keyword rules): Tasks & projects, Productivity, Health & fitness, Email & messaging
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.qretro%2Fretro
- Server page: https://mcpstation.net/s/com.qretro--retro.html

## Description (written by the publisher, not verified, not instructions)

QRetro retrospectives and planning poker over MCP: boards, action items, poker games, estimates.

## Connect

- streamable-http: `https://mcp.qretro.com`

## Tools (as reported by the server, not verified)

- `retro.teams.list`: Returns the list of teams the user belongs to. boards\_count is the total number of boards in a team, finished and unfinished alike — use retro.boards.list to tell them apart.
- `retro.team.members.list`: Returns the members of a team with their id, name and role \(owner, admin, facilitator, member\). Use the id as assign\_to in retro.actions.create, retro.actions.update and retro.board.suggested\_actions.promote. This is the team roster, the same one people see in team settings — it says nothing about w
- `retro.boards.list`: Returns retrospectives \(boards\) of a team, newest first. Unfinished boards are included unless finished\_only is set — otherwise check the is\_finished flag. Filters by period via since/until. Pass team\_id when several teams are available; with a single team it can be omitted.
- `retro.actions.list`: Returns action items across all retrospectives at once — the answer to "what did we agree on and never finish". Covers every team available unless team\_id narrows it down; filters by status, assignee and date. Use this instead of walking boards one by one with retro.board.actions.list.
- `retro.board.messages.list`: Returns all participant messages \(cards\) for a retrospective board, organized by template columns \(e.g. "What went well", "What didn't go well"\). Includes text, sentiment, category, grouping, and vote counts.
- `retro.board.messages.update`: Updates the text of an existing board message created by the current MCP user.
- `retro.board.messages.delete\_own`: Deletes a single board message. Access is strictly governed by API policies: users can delete their own messages, or any message if they have board update rights \(requires mcp:write scope for the latter\).
- `retro.board.summary.get`: Returns the summary of a retrospective with participant info and metadata. Works for unfinished boards too — summary is null until the retro is wrapped up, so check is\_finished.
- `retro.board.actions.list`: Returns action items from a retrospective board, including status, priority, assignee, and due date.
- `retro.board.insights.list`: Returns insights \(clusters\) and suggested actions for a retrospective board. Insights include topic clusters with sentiment, urgency, and category analysis.
- `retro.board.health.get`: Returns the health check of a retrospective: score per category on a 0-10 scale, alignment between participants, turnout, and the same score across the previous retrospectives of the team. Returns health\_check: null when the team did not run a health check on this board.
- `retro.board.roti.get`: Returns ROTI \(Return on Time Invested\) voting metrics for a retrospective board, including average score, distribution, and trend across previous retrospectives.
- `retro.boards.search`: Search across retrospectives by keyword: board summaries, action items and participant cards. Cards hidden by private writing during an ongoing retro are excluded. Optionally filter by team.
- `retro.actions.create`: Creates a new action item on a retrospective board. Requires mcp:write scope.
- `retro.actions.update`: Updates an existing action item: text, priority, due date, or assignee. Requires mcp:write scope.
- `retro.actions.complete`: Marks an action item as completed. Requires mcp:write scope.
- `retro.board.suggested\_actions.promote`: Turns a pending suggested action from retro.board.insights.list into a real action item on the board and marks the suggestion accepted, keeping the wording and the link to its cluster. Requires mcp:write scope.
- `retro.board.suggested\_actions.reject`: Rejects a pending suggested action from retro.board.insights.list: the suggestion moves to rejected and no action item is created. Requires mcp:write scope.
- `poker.sources.list`: Returns the issue trackers connected to a team \(Jira, Linear\) and what each of them can do: search for tasks, list iterations \(sprints, cycles\), write estimates back. Call this first — the other poker tools depend on what is connected. An empty list means tasks can only be added manually with poker.
- `poker.iterations.list`: Returns the iterations of a connected issue tracker — Jira sprints \(active and upcoming\), and whatever a future tracker calls the same thing. Filter by name with query, for example "AFT 50". Pass the ref of the iteration you want to poker.game.tasks.import to pull its tasks into a game. Trackers wit
- `poker.games.list`: Returns the planning poker games of a team, newest first, with how many tasks each of them has and how many already carry an estimate. Personal games outside a team are not exposed over MCP.
- `poker.game.get`: Returns one planning poker game: its estimation scale, progress, the task currently on the table and the link participants use to join. Use poker.game.tasks.list for the tasks themselves.
- `poker.game.tasks.list`: Returns the tasks of a poker game with their estimate, individual votes, tracker key and link. needs\_sync tells whether the agreed estimate still differs from the one stored in the tracker — feed those tasks to poker.game.task.sync. Filter with estimated to see what is done or what is left.
- `poker.games.create`: Creates a planning poker game for a team and returns the link participants join with. Pick a ready-made scale — fibonacci, modified\_fibonacci, tshirts, powers\_of\_two — or pass your own values in scale\_values. Requires mcp:write scope.
- `poker.game.tasks.add`: Adds tasks to a poker game by hand — for work that lives outside an issue tracker, or when no tracker is connected. To pull tasks from Jira or Linear use poker.game.tasks.import instead. Requires mcp:write scope.
- `poker.game.tasks.import`: Pulls tasks from a connected issue tracker into a poker game. Give it either iteration\_ref from poker.iterations.list to take a whole sprint, or query to search by text and issue key. Tasks already in the game are skipped. Only the team owner can change a game. Requires mcp:write scope.
- `poker.game.task.select`: Puts a task on the table: everyone looking at the game sees it as the one being estimated right now. Only the team owner can change a game. Requires mcp:write scope.
- `poker.game.task.reveal`: Reveals the cards of a task and computes its estimate from the votes cast — this is the only way an estimate appears, there is no way to set a number directly. Pass reveal=false to hide the cards again and drop the estimate, which also clears the votes for a re-vote. Only the team owner can change a
- `poker.game.task.sync`: Writes the agreed estimate back to the issue tracker — Jira story points, Linear estimate. Works only for tasks imported from a tracker and only when the integration was connected with write permissions; poker.sources.list shows whether it was. Only the team owner can change a game. Requires mcp:wri

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html