Productivity

qretro.com

A free online retrospective tool with templates, voting, and integrations for Agile teams.

1 endpoint29 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://mcp.qretro.com

No auth detected

MCP server metadata

Name: QRetro.com
Version: 1.3.0

Capabilities

toolsresourcesprompts

Server instructions

MCP server for retrospectives and planning poker. Tool names follow the domain.scope.action convention (for example, retro.teams.list, poker.games.list). API tokens can be scoped to specific teams — if your token is team-scoped, only data from those teams is accessible. Start with retro.teams.list to discover available teams. Retrospectives: retro.boards.list shows completed and ongoing boards. For each board you can call retro.board.messages.list, retro.board.summary.get, retro.board.actions.list, retro.board.insights.list, retro.board.health.get, and retro.board.roti.get. Use retro.boards.search to find retrospectives by keyword. retro.team.members.list gives the team roster — take user IDs from it for the assign_to argument. With write scope you can use retro.actions.create, retro.actions.update, retro.actions.complete, retro.board.messages.update, and retro.board.messages.delete_own. Working through a board: read it with retro.board.messages.list and retro.board.summary.get, then call retro.board.insights.list — its suggested_actions with status "pending" are the system's proposals. Turn the ones the team agrees on into real action items with retro.board.suggested_actions.promote (it keeps the wording and the link to the cluster, so do not retype them through retro.actions.create), and drop the rest with retro.board.suggested_actions.reject. Both need the team owner or a facilitator, as in the interface. Planning poker: poker.sources.list tells which issue trackers a team has connected and what each can do — call it before anything that touches Jira or Linear. To prepare a session: poker.iterations.list to find a sprint, poker.games.create to open a game, poker.game.tasks.import to pull the sprint tasks into it (or poker.game.tasks.add for tasks that live outside a tracker). Give participants the url returned by the game tools. During the session: poker.game.task.select, then poker.game.task.reveal once people have voted, then poker.game.task.sync to write the estimate back to the tracker. Estimates come only from revealed votes — there is no tool to set a number directly, and no tool to vote on behalf of the client. Every poker tool that changes a game requires the caller to be the team owner.

Known tools 29

retro.teams.list

Returns the list of teams the user belongs to.

Inferred read-only

retro.team.members.list

Returns the members of a team with their id, name and role (owner, admin, facilitator, member).

Inferred read-only

retro.boards.list

Returns retrospectives (boards) of a team, newest first.

Inferred read-only

retro.actions.list

Returns action items across all retrospectives at once — the answer to "what did we agree on and never finish".

Inferred read-only

retro.board.messages.list

Returns all participant messages (cards) for a retrospective board, organized by template columns (e.

Inferred read-only

retro.board.messages.update

Updates the text of an existing board message created by the current MCP user.

Potential side effects

retro.board.messages.delete_own

Deletes a single board message.

Potential side effects

retro.board.summary.get

Returns the summary of a retrospective with participant info and metadata.

Inferred read-only

retro.board.actions.list

Returns action items from a retrospective board, including status, priority, assignee, and due date.

Inferred read-only

retro.board.insights.list

Returns insights (clusters) and suggested actions for a retrospective board.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

retro.boards.search

Search across retrospectives by keyword: board summaries, action items and participant cards.

Inferred read-only

retro.actions.create

Creates a new action item on a retrospective board.

Potential side effects

retro.actions.update

Updates an existing action item: text, priority, due date, or assignee.

Potential side effects

retro.actions.complete

Marks an action item as completed.

Inferred read-only

retro.board.suggested_actions.promote

Turns a pending suggested action from retro.

Inferred read-only

retro.board.suggested_actions.reject

Rejects a pending suggested action from retro.

Inferred read-only

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.

Potential side effects

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.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

poker.game.tasks.list

Returns the tasks of a poker game with their estimate, individual votes, tracker key and link.

Inferred read-only

poker.games.create

Creates a planning poker game for a team and returns the link participants join with.

Potential side effects

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.

Inferred read-only

poker.game.tasks.import

Pulls tasks from a connected issue tracker into a poker game.

Inferred read-only

poker.game.task.select

Puts a task on the table: everyone looking at the game sees it as the one being estimated right now.

Inferred read-only

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.

Inferred read-only

poker.game.task.sync

Writes the agreed estimate back to the issue tracker — Jira story points, Linear estimate.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.qretro-com]
url = "https://mcp.qretro.com"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "qretro-com": {
      "type": "http",
      "url": "https://mcp.qretro.com"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: qretro-com
Remote MCP URL: https://mcp.qretro.com

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "qretro-com": {
      "url": "https://mcp.qretro.com"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "qretro-com": {
      "type": "http",
      "url": "https://mcp.qretro.com"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "qretro-com",
  "transport": "streamable-http",
  "url": "https://mcp.qretro.com"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for qretro.com was fetched 2026-08-23T15:52:52.087Z.

Trust status Trusted

qretro.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.