Retro is answering right now. Last checked 3 min ago. It exposes 29 tools.
QRetro retrospectives and planning poker over MCP: boards, action items, poker games, estimates.
Uptime history
91 days of history · worst day 0%
91 days agonow
100.0%
Uptime 24h
92 of 92 checks
29
Tools
read from the server
460 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 5
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 2 November 2026. No other catalogue keeps this.
7 Nov
4 tool descriptions were rewritten
poker.game.task.reveal, poker.game.task.select, poker.game.tasks.import and 1 more
2 Nov
a tool changed version
Retro missed one check this week
Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.
run in your terminal
claude mcp add retro --transport http https://mcp.qretro.comSettings → Connectors → Add custom connector, then paste this address
https://mcp.qretro.com~/.codex/config.toml
[mcp_servers.retro]
url = "https://mcp.qretro.com".cursor/mcp.json
{
"mcpServers": {
"retro": {
"url": "https://mcp.qretro.com"
}
}
}.vscode/mcp.json
{
"servers": {
"retro": {
"type": "http",
"url": "https://mcp.qretro.com"
}
}
}Available tools 29
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
retro
retro.actions.complete
Marks an action item as completed. Requires mcp:write scope.
retro.actions.create
Creates a new action item on a retrospective board. Requires mcp:write scope.
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.actions.update
Updates an existing action item: text, priority, due date, or assignee. Requires mcp:write scope.
retro.board.actions.list
Returns action items from a retrospective board, including status, priority, assignee, and due date.
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.insights.list
Returns insights (clusters) and suggested actions for a retrospective board. Insights include topic clusters with sentiment, urgency, and category analysis.
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.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.roti.get
Returns ROTI (Return on Time Invested) voting metrics for a retrospective board, including average score, distribution, and trend across previous retrospectives.
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.
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.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.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.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 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.
poker
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.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 or an admin 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 or an admin can change a game. Requires mcp:write scope.
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 or an admin can change a game. 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 or an admin can change a game. Requires mcp:write scope.
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.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.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 without iteration support (currently Linear) return an empty list — search by text instead.
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.game.tasks.add.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.qretro.com | streamable-http | answering | 383 ms | 3 min ago |
Alternatives to Retro
same job, measured the same wayVondet
by vondet
A project planning board your AI reads and updates over MCP, so the plan stays one plan.
Favro
by mmedum
Favro cards, boards and collections over MCP: read, search, write, and resolve names to ids.
Azure Boards MCP
by broisnischal
Azure DevOps Boards work items over MCP (stdio). Requires Bun, org, project, and PAT.
Toofi Dental Planning MCP
by toofi
Agent-native dental planning MCP for plan drafts, presentations, and price estimates.
McpStamp Kanban Board
by theluckystrike
Task boards per project: priorities, due dates, estimates, overdue tasks and a weekly review.
Parabol MCP by usefulapi
by usefulapi
Start Parabol retrospectives, standups and sprint poker; read teams/meetings/tasks; create tasks.
Estimay
by estimay
Planning poker rooms: import stories from Jira or GitHub, run rounds, write the estimates back.
Metro MCP
by steve228uk
MCP server for React Native/Expo runtime debugging, inspection, and automation via Metro/CDP
Retro — questions
Answers built from our own checks of this server.
What can Retro do?
It exposes 29 tools, read directly from the server on our last check. Among them: poker.game.get, poker.games.create, poker.games.list, poker.game.task.reveal, poker.game.tasks.add, poker.game.task.select and 23 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Retro mostly used for?
Its tools cluster around retro and poker. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Retro working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 460 ms. The bar chart above shows every period we have measured.
How do I connect Retro?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Retro need an API key?
No. Retro completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 29 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Retro?
It answers our handshake in 460 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.