# retro MCP server

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

## Links
- Registry page: https://www.getdrio.com/mcp/com-qretro-retro
- Website: https://qretro.com

## Install
- Endpoint: https://mcp.qretro.com
- Auth: Not captured

## Setup notes
- Remote endpoint: https://mcp.qretro.com

## Tools
- retro.teams.list (List Teams Tool) - 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. Endpoint: https://mcp.qretro.com
- retro.team.members.list (List Team Members Tool) - 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. Endpoint: https://mcp.qretro.com
- retro.boards.list (List Boards Tool) - 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. Endpoint: https://mcp.qretro.com
- retro.actions.list (List Actions Tool) - 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. Endpoint: https://mcp.qretro.com
- retro.board.messages.list (Get Board Messages Tool) - 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. Endpoint: https://mcp.qretro.com
- retro.board.messages.update (Update Message Tool) - Updates the text of an existing board message created by the current MCP user. Endpoint: https://mcp.qretro.com
- retro.board.messages.delete_own (Delete Own Message Tool) - 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). Endpoint: https://mcp.qretro.com
- retro.board.summary.get (Get Board Summary Tool) - 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. Endpoint: https://mcp.qretro.com
- retro.board.actions.list (Get Board Actions Tool) - Returns action items from a retrospective board, including status, priority, assignee, and due date. Endpoint: https://mcp.qretro.com
- retro.board.insights.list (Get Board Insights Tool) - Returns insights (clusters) and suggested actions for a retrospective board. Insights include topic clusters with sentiment, urgency, and category analysis. Endpoint: https://mcp.qretro.com
- retro.board.health.get (Get Board Health Tool) - 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. Endpoint: https://mcp.qretro.com
- retro.board.roti.get (Get Board Roti Tool) - Returns ROTI (Return on Time Invested) voting metrics for a retrospective board, including average score, distribution, and trend across previous retrospectives. Endpoint: https://mcp.qretro.com
- retro.boards.search (Search Boards Tool) - 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. Endpoint: https://mcp.qretro.com
- retro.actions.create (Create Action Item Tool) - Creates a new action item on a retrospective board. Requires mcp:write scope. Endpoint: https://mcp.qretro.com
- retro.actions.update (Update Action Item Tool) - Updates an existing action item: text, priority, due date, or assignee. Requires mcp:write scope. Endpoint: https://mcp.qretro.com
- retro.actions.complete (Complete Action Item Tool) - Marks an action item as completed. Requires mcp:write scope. Endpoint: https://mcp.qretro.com
- retro.board.suggested_actions.promote (Promote Suggested Action Tool) - 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. Endpoint: https://mcp.qretro.com
- retro.board.suggested_actions.reject (Reject Suggested Action Tool) - 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. Endpoint: https://mcp.qretro.com
- poker.sources.list (List Poker Sources Tool) - 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. Endpoint: https://mcp.qretro.com
- poker.iterations.list (List Poker Iterations Tool) - 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. Endpoint: https://mcp.qretro.com
- poker.games.list (List Poker Games Tool) - 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. Endpoint: https://mcp.qretro.com
- poker.game.get (Get Poker Game Tool) - 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. Endpoint: https://mcp.qretro.com
- poker.game.tasks.list (List Poker Tasks Tool) - 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. Endpoint: https://mcp.qretro.com
- poker.games.create (Create Poker Game Tool) - 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. Endpoint: https://mcp.qretro.com
- poker.game.tasks.add (Add Poker Tasks Tool) - 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. Endpoint: https://mcp.qretro.com
- poker.game.tasks.import (Import Poker Tasks Tool) - 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. Endpoint: https://mcp.qretro.com
- poker.game.task.select (Select Poker Task Tool) - 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. Endpoint: https://mcp.qretro.com
- poker.game.task.reveal (Reveal Poker Task Tool) - 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. Endpoint: https://mcp.qretro.com
- poker.game.task.sync (Sync Poker Estimate Tool) - 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. Endpoint: https://mcp.qretro.com

## Resources
Not captured

## Prompts
- analyze-retro - Analyze Retro Prompt Analyze a specific retrospective board: fetch summary, insights, action items, and provide a structured analysis. Arguments: board_id
- team-health - Team Health Prompt Analyze team health trends across multiple retrospectives. Compare health scores, ROTI metrics, and action item completion over time. Arguments: team_id

## Metadata
- Owner: com.qretro
- Version: 1.3.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Aug 2, 2026
- Source: https://registry.modelcontextprotocol.io