QRetro

Claude Desktop(claude_desktop_config.json):

{ "mcpServers": { "qretro": { "url": "https://mcp.qretro.com", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } }

claude mcp add --transport http qretro https://mcp.qretro.com --header "Authorization: Bearer YOUR_TOKEN"

Once connected, you can query the system with questions like:

- "Show me the retrospectives for the Backend team"
- "What actions were agreed on in the last sprint?"
- "How has our team health changed over the last 3 months?"
- "Search all retros for mentions of deployment problems"

Every documentation page has an action block in the top-right corner:

- Copy page– copies the full page in Markdown format. Useful when you want to “attach” this documentation to a session in Claude, Cursor, or ChatGPT.
- Copy Markdown link– copies a direct link to the Markdown version of the page (for example,https://qretro.com/raw/en/docs/6.mcp.md) that you can pass to an assistant with a request like “Read this MCP documentation and use it as a reference”.
- Open in ChatGPT / Open in Claude– open the selected assistant with a pre-filled query likeRead https://qretro.com/raw/en/docs/6.mcp.md so I can ask questions about it..

Recommended text for using this documentation inside an MCP client (Claude Desktop, Cursor, etc.):

Read the documentation for the QRetro MCP server here: https://qretro.com/raw/en/docs/6.mcp.md Use it as the source of truth about available tools and their parameters when working with the QRetro server.

All tools follow thedomain.scope.actionnaming convention. QRetro has two domains:retrofor retrospectives andpokerfor planning poker.

MCP tools use theretro.andpoker.naming patterns, for exampleretro.teams.listandpoker.games.list. Always use these names in MCP clients.

Suggestions the system puts together after a retrospective start out as pending:retro.board.insights.listshows them, promote turns one into an agreement on the board without retyping it, reject dismisses it. Both are limited to the people who can change the board, exactly as in the interface, and a suggestion can only be handled once.

Two things the poker tools deliberately cannot do: set an estimate directly (it only ever comes from revealed votes) and vote on your behalf. Changing a game — importing tasks, revealing cards, syncing estimates — is limited to the team owner, exactly as in the interface.

QRetro also provides built-in prompts that guide your client through structured analysis. Clients that support MCP prompts pick them up as ready-made commands, so there is nothing to install and nothing to phrase yourself. In Claude Code, press/and they appear in the list next to the built-in commands as/mcp__qretro__analyze-retroand/mcp__qretro__team-health— the prefix is built from the name you gave the server when adding it.

- analyze-retro— deep-dive into a single retrospective: summary, clusters, agreements, health and ROTI in one pass, ending with key themes, risks and what to change next time. Takesboard_id.
- team-health— health trends across the team's last retrospectives: where scores and ROTI are heading, how many agreements actually get closed, what keeps repeating. Takesteam_id.

Access is always limited by two things at once: the permissions granted to the client, and your own membership in teams. A client can never reach a team you do not belong to.

Tools a client has no permission for are not offered to it at all — withoutmcp:writeit will not even seeretro.actions.create.

Permissions match the interface exactly: a client can do only what you could do yourself on the same board. Editing an agreement is limited to its author and the board owner, closing one is also available to the assignee, and cards hidden by private writing during an ongoing retro stay invisible — including in search.

There is nothing to type: the application asks for the permissions it needs, and you see them on the approval screen before agreeing. Deleting messages is not available this way — grant it with an API token if a client really needs it.

Additional guidelines for assistant clients

- Source of truth for permissions: when working with action items, treat thecan_editandcan_completeflags on ActionItem objects (and API responses) as the single source of truth. Do not invent custom permission logic in prompts.
- Team context: most tools implicitly assume a single team (Team) context. A signed-in connection always covers every team you belong to, so start withretro.teams.listand passteam_idexplicitly; tools that need a team will name the available ones if you omit it.
- Call chains: before updating or deleting entities, always fetch lists first (retro.boards.list,retro.board.actions.list,retro.board.messages.list) to obtain fresh IDs. To put a name on an agreement, take the user ID fromretro.team.members.list—assign_toaccepts that ID orme.

When a user asks to “analyze the team’s health”, follow this sequence:
- Callretro.teams.list, thenretro.boards.listwith the chosenteam_id(it can be omitted only when a single team is available).
- Callretro.board.health.getfor the latest board — itstrendalready carries the score of the previous retrospectives, so there is no need to walk them one by one. Addretro.board.roti.getif you also want the perceived value of the meetings.
- Ifhealth_checkreturnsnull, do not report an error. Instead answer:“Health surveys were not run for this board yet”and continue the analysis based on available data (cards, summary, action items).

Recipe B: What we agreed on and never finished

Recipe C: Set up planning poker for a sprint

When a user says something like “set up planning poker for NEXT AFT 50”:
- Callpoker.sources.listto see what the team has connected. An empty list is not a dead end — skip to step 3 and add tasks withpoker.game.tasks.add.
- Callpoker.iterations.listwithquery: "AFT 50"and take therefof the matching sprint. Trackers without sprint support return an empty list — use a textqueryin the next step instead.
- Callpoker.games.createwith the sprint name, thenpoker.game.tasks.importwith thatref.
- Hand theurlfrom the response to the team — that is where people vote.
- Once votes are in:poker.game.task.select,poker.game.task.reveal, andpoker.game.task.syncfor every task whoseneeds_syncis true.

Connect with 10,000+ tools across HRIS, ATS, CRM, Accounting, Calendar, Meeting, Ticketing, and more categories.

Connect any AI assistant to Syncro: manage tickets, invoices, customers, assets, and more.

Multi-device file sync, dev-doc CRUD, task management, and session handoffs for AI agents - MCP + OpenAPI dual surface.

Decispher captures the decisions, conventions, and constraints from the conversations your team is already having in Slack, GitHub, GitLab, and Jira, then serves them back to every human and every agent that needs them. Automatically.

Hosted MCP server for Duvo — start runs, inspect approvals, and expose grocery/retail execution tools to compatible agents.

MCP server to connect to and use any public GitHub repo as knowledge base (markdown/notebook docs)

Create, edit, inspect, and publish collaborative HTML documents from AI agents.

Create presentations, docs, sheets and meeting notes from chat — with a hosted share link, an editor, and PPTX/PDF export.