retro
com.qretro/retroVersion 1.4.0QRetro retrospectives and planning poker over MCP: boards, action items, poker games, estimates.
Status
Responds335 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:11 UTC
- Latency
- 335 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.qretro.com/Responds335 msNo sign-in
Claude Code
claude mcp add --transport http retro https://mcp.qretro.com/Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: retro
Remote MCP server URL: https://mcp.qretro.com/Cursor
{
"mcpServers": {
"retro": {
"url": "https://mcp.qretro.com/"
}
}
}VS Code
code --add-mcp '{"name":"retro","type":"http","url":"https://mcp.qretro.com/"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
29 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
poker.game.getReturns 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. | Not declared | Yes | Not declared | Not declared |
poker.game.task.revealReveals 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 or an admin can change a game. Requires mcp:write scope. | Not declared | Not declared | Yes | Not declared |
poker.game.task.selectPuts a task on the table: everyone looking at the game sees it as the one being estimated right now. Only the team owner or an admin can change a game. Requires mcp:write scope. | No | Not declared | Yes | Not declared |
poker.game.task.syncWrites 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 or an admin can change a game. Requires mcp:write scope. | Yes | Not declared | Yes | Yes |
poker.game.tasks.addAdds 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. | No | Not declared | Not declared | Not declared |
poker.game.tasks.importPulls 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 or an admin can change a game. Requires mcp:write scope. | No | Not declared | Yes | Yes |
poker.game.tasks.listReturns 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. | Not declared | Yes | Not declared | Not declared |
poker.games.createCreates 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. | No | Not declared | Not declared | Not declared |
poker.games.listReturns 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. | Not declared | Yes | Not declared | Not declared |
poker.iterations.listReturns 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. | Not declared | Yes | Not declared | Not declared |
poker.sources.listReturns 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. | Not declared | Yes | Not declared | Not declared |
retro.actions.completeMarks an action item as completed. Requires mcp:write scope. | No | Not declared | Yes | Not declared |
retro.actions.createCreates a new action item on a retrospective board. Requires mcp:write scope. | No | Not declared | Not declared | Not declared |
retro.actions.listReturns 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. | Not declared | Yes | Not declared | Not declared |
retro.actions.updateUpdates an existing action item: text, priority, due date, or assignee. Requires mcp:write scope. | Not declared | Not declared | Yes | Not declared |
retro.board.actions.listReturns action items from a retrospective board, including status, priority, assignee, and due date. | Not declared | Yes | Not declared | Not declared |
retro.board.health.getReturns 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. | Not declared | Yes | Not declared | Not declared |
retro.board.insights.listReturns insights (clusters) and suggested actions for a retrospective board. Insights include topic clusters with sentiment, urgency, and category analysis. | Not declared | Yes | Not declared | Not declared |
retro.board.messages.delete_ownDeletes 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). | Yes | Not declared | Not declared | Not declared |
retro.board.messages.listReturns 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. | Not declared | Yes | Not declared | Not declared |
retro.board.messages.updateUpdates the text of an existing board message created by the current MCP user. | Not declared | Not declared | Yes | Not declared |
retro.board.roti.getReturns ROTI (Return on Time Invested) voting metrics for a retrospective board, including average score, distribution, and trend across previous retrospectives. | Not declared | Yes | Not declared | Not declared |
retro.board.suggested_actions.promoteTurns 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. | No | Not declared | Not declared | Not declared |
retro.board.suggested_actions.rejectRejects a pending suggested action from retro.board.insights.list: the suggestion moves to rejected and no action item is created. Requires mcp:write scope. | Yes | Not declared | Not declared | Not declared |
retro.board.summary.getReturns 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. | Not declared | Yes | Not declared | Not declared |
retro.boards.listReturns 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. | Not declared | Yes | Not declared | Not declared |
retro.boards.searchSearch 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. | Not declared | Yes | Not declared | Not declared |
retro.team.members.listReturns 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. | Not declared | Yes | Not declared | Not declared |
retro.teams.listReturns 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. | Not declared | Yes | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Repository
- Not given
- Categories (suggested)
- CommunicationSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared