Agents Index

Retro

Online

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

Visit publisherConnectJSON

What it can do: 29 tools

  • retro.teams.list read-onlyReturns 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 read-onlyReturns 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
  • retro.boards.list read-onlyReturns 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 tea
  • retro.actions.list read-onlyReturns 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 i
  • retro.board.messages.list read-onlyReturns 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.updateUpdates the text of an existing board message created by the current MCP user.
  • 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).
  • retro.board.summary.get read-onlyReturns 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 read-onlyReturns action items from a retrospective board, including status, priority, assignee, and due date.
  • retro.board.insights.list read-onlyReturns insights (clusters) and suggested actions for a retrospective board. Insights include topic clusters with sentiment, urgency, and category analysis.
  • retro.board.health.get read-onlyReturns 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
  • retro.board.roti.get read-onlyReturns ROTI (Return on Time Invested) voting metrics for a retrospective board, including average score, distribution, and trend across previous retrospectives.
  • retro.boards.search read-onlySearch 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.createCreates a new action item on a retrospective board. Requires mcp:write scope.
  • retro.actions.updateUpdates an existing action item: text, priority, due date, or assignee. Requires mcp:write scope.
  • retro.actions.completeMarks an action item as completed. Requires mcp:write scope.
  • 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.
  • 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.
  • poker.sources.list read-onlyReturns 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 wha
  • poker.iterations.list read-onlyReturns 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
  • poker.games.list read-onlyReturns 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 read-onlyReturns 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 read-onlyReturns 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.gam
  • 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 mc
  • 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.
  • 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 skippe
  • 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.
  • 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 estim
  • 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.li

Connect it

Claude Code
claude mcp add --transport http retro https://mcp.qretro.com
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.qretro.com
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "retro": {
      "url": "https://mcp.qretro.com"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "retro": {
      "type": "http",
      "url": "https://mcp.qretro.com"
    }
  }
}

Questions

What does Retro do?

QRetro retrospectives and planning poker over MCP: boards, action items, poker games, estimates. It exposes 29 tools to AI assistants.

What tools does Retro provide?

29 tools, including 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, retro.board.actions.list, retro.board.insights.list, retro.board.health.get, retro.board.roti.get….

How do I connect Retro to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.qretro.com as a custom connector or MCP server. Copy-paste setup is on this page.

Does Retro require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Retro online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Retro?

qretro.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Productivity & Docs