mcp server
retro
QRetro retrospectives and planning poker over MCP: boards, action items, poker games, estimates.
Description as published by the maintainer. Source
- version 1.3.0
- active
active — Registry entry last updated 2026-08-02.
What this server can do
29 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
poker.game.get(game_id)- 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. Required: game_id.
poker.game.task.reveal(reveal, game_id, task_id)- 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 game. Requires mcp:write scope. Required: game_id, task_id.
poker.game.task.select(game_id, task_id)- 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. Required: game_id, task_id.
poker.game.task.sync(game_id, task_id)- 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:write scope. Required: game_id, task_id.
poker.game.tasks.add(tasks, game_id)- 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. Required: game_id, tasks.
poker.game.tasks.import(limit, query, source, game_id, iteration_ref)- 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. Required: game_id.
poker.game.tasks.list(limit, game_id, estimated)- 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. Required: game_id.
poker.games.create(name, scale, team_id, scale_values)- 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. Required: name.
poker.games.list(limit, team_id)- 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.iterations.list(query, source, team_id)- 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 without iteration support (currently Linear) return an empty list — search by text instead.
poker.sources.list(team_id)- 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.game.tasks.add.
retro.actions.complete(action_item_id)- Marks an action item as completed. Requires mcp:write scope. Required: action_item_id.
retro.actions.create(due, text, board_id, priority, assign_to)- Creates a new action item on a retrospective board. Requires mcp:write scope. Required: board_id, text.
retro.actions.list(limit, since, status, team_id, assignee)- 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.actions.update(due, text, priority, assign_to, action_item_id)- Updates an existing action item: text, priority, due date, or assignee. Requires mcp:write scope. Required: action_item_id.
retro.board.actions.list(board_id, include_completed)- Returns action items from a retrospective board, including status, priority, assignee, and due date. Required: board_id.
retro.board.health.get(board_id)- 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. Required: board_id.
retro.board.insights.list(board_id)- Returns insights (clusters) and suggested actions for a retrospective board. Insights include topic clusters with sentiment, urgency, and category analysis. Required: board_id.
retro.board.messages.delete_own(message_id)- 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). Required: message_id.
retro.board.messages.list(board_id)- 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. Required: board_id.
retro.board.messages.update(text, message_id)- Updates the text of an existing board message created by the current MCP user. Required: message_id, text.
retro.board.roti.get(board_id)- Returns ROTI (Return on Time Invested) voting metrics for a retrospective board, including average score, distribution, and trend across previous retrospectives. Required: board_id.
retro.board.suggested_actions.promote(board_id, assign_to, suggested_action_id)- 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. Required: board_id, suggested_action_id.
retro.board.suggested_actions.reject(board_id, suggested_action_id)- 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. Required: board_id, suggested_action_id.
retro.board.summary.get(board_id)- 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. Required: board_id.
retro.boards.list(since, until, team_id, finished_only)- 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.boards.search(query, team_id)- 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. Required: query.
retro.team.members.list(team_id)- 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 who wrote which card. Pass team_id when several teams are available; with a single team it can be omitted.
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.
Last successful function declaration observed on . Source: https://mcp.qretro.com. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.qretro.com.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.3.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-02 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-02 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 29 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.qretro.com | |
| mcp endpoint status | ok | The server listed 29 functions when asked. | as of probe | mcp.qretro.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json