Reviews
No review yet. Used retro? Be the first to help others choose.What it does
retro is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)Hosted endpoint
https://mcp.qretro.comstreamable-http
In Claude Code: claude mcp add --transport http retro https://mcp.qretro.com
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"retro": {
"url": "https://mcp.qretro.com"
}
}
}Live check
Electra Index connected to the hosted endpoint 2d agoONLINE retro answered an MCP connection on 14 Nov 2026 and introduced itself as QRetro.com 1.4.0 (MCP protocol 2025-06-18).
29 tools offered to AI assistants
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 saretro.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; wiretro.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 boretro.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 ruretro.board.roti.get· Returns ROTI (Return on Time Invested) voting metrics for a retrospective board, including average score, distribution, and trend across previous retrospectives.
Show 17 more
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 epoker.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.gpoker.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. Filterpoker.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 ownpoker.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 or an admin 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 cleapoker.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
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.4.0 | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| Hosted endpoint | https://mcp.qretro.com | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| Website | https://qretro.com | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 10h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 10h ago |
Change history
- VERSION02 Nov 20261.3.0 → 1.4.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is retro still online?
Free alerts · no account▲ 0Do you run retro? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about retro
How do I connect retro?
Use the hosted endpoint https://mcp.qretro.com in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does retro offer?
When Electra Index connected on 14 Nov 2026, it listed 29 tools: retro.teams.list, retro.team.members.list, retro.boards.list, retro.actions.list, retro.board.messages.list, retro.board.messages.update, retro.board.messages.delete_own, retro.board.summary.get and more. The full list is in "Live check" above.
Is retro online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.