Ask your AI assistant about your teams

Connect TeamRetro to Claude, ChatGPT, Microsoft Copilot, Gemini or any MCP-compatible assistant. Summarize retros, chase actions and track team health — from chat, with the TeamRetro MCP server.

Try TeamRetro free Read the docs

  1. Summarize the Mobile team's last retro and list the actions we agreed on.

    • list_retrospectives
    • get_retrospective

    Here's the Mobile team's retro from last Thursday — 8 contributors, 14 ideas, 3 actions:

    Actions agreed

    • Fix flaky CI — owner Sam, due Friday
    • PR review within one day — owner Marcus
    • Observability budget — parked for the next retro
Illustrative example — TeamRetro over MCP in Assistant

Your retros, health checks and actions — now a question away

TeamRetro speaks MCP, so the assistant you already work in can read your retros, summarize meetings, chase actions and keep working agreements current. No new dashboard to open, no context-switch.

With TeamRetro MCP you can…

See across every team

Ask which teams need attention and get overdue retros, slipping health scores and stalled actions, already flagged. Cross-team views are an Enterprise capability.

Run your rituals from chat

Spin up a retro, health check or planning poker session using the same template as last time — ready to join.

Set up estimation from your backlog

Hand the assistant this sprint’s stories and have it open a planning poker session, ready for the team to vote.

Never lose a follow-up

Check what’s on your plate, mark actions done and push due dates. Park an idea for the next retro the moment it comes up.

Participate, not just observe

Cast votes, rate health-check dimensions and leave feedback as yourself — every contribution respects your team’s anonymity settings.

Connect it to everything else

Pull incidents from Slack into the retro, post summaries to your channel, cross-check actions against the Jira tickets they reference.

Three prompts your team will run every week

Summarize our last retro

  • What did we commit to last retro, and who owns each action?

Runs list_retrospectives → get_retrospective and hands back the summary with owners and due dates.

Start the next one

  • Start a retro for the Platform team using the same template as last time

Sets up the meeting, ready to share — no template hunting.

Park it before it’s lost

  • Park 'observability budget' for our next retro

Captures the topic as a parked item the moment it comes up in conversation.

Prompts for every role

Engineering managers & coaches Enterprise

  • How are my teams doing? Flag anything that needs attention
  • Which teams have health scores trending down this quarter?
  • How's our action follow-through across all teams in the last 90 days?
  • Has any team gone quiet — no activity in the past month?

Scrum masters & facilitators

  • Summarize our last retro and list the actions we committed to
  • Compare the Mobile team's last three retros — what themes keep coming up?
  • Start a planning poker session from this sprint's backlog stories
  • Set up a health check for the API team, same model as last time
  • What's in our parking lot for the next retro?

Team members

  • What's on my plate? Show my open and overdue actions
  • Mark my action about the onboarding docs as done
  • Rate Communication a 7 on this week's health check
  • Add my vote to the idea about deployment pain

Working agreements

  • What working agreements does the API team have?
  • We agreed to keep PRs under 400 lines — add it as a working agreement
  • Reword our standup agreement to say cameras are optional

Integrates with your existing workflows

Push action items with owners and due dates, agreements, meeting summaries, and health-check results straight into the tools your team already runs on — task trackers, chat, docs, and exports. Connect over our API, webhooks, or MCP so AI agents can pick up where the meeting left off.

Project & issue tracking

Jira GitHub GitLab DevOps Linear Trello Asana ClickUp monday.com Shortcut Basecamp

Chat & docs

Slack Teams Confluence Notion

Automation & AI

Connect via

REST API Webhooks MCP

AI agents & tools

Claude ChatGPT Copilot Gemini
Your whole stack

Export & formats

Excel CSV PDF Markdown Email

  1. Read this week's #incidents channel and park the top themes for the Platform team's next retro.

    • create_parked_item

    Found three recurring themes in #incidents and parked them for the Platform team:

    Parked for next retro

    • Deploy rollbacks took too long
    • Alert noise during the migration
    • On-call handover gaps
Illustrative example — TeamRetro over MCP in Assistant

Bring the signal in, push the outcomes out

Your other tools hold the raw signal; TeamRetro is where the team acts on it. Pull incidents from Slack and park the themes. Turn a postmortem’s commitments into actions with owners and due dates. Post Friday’s retro summary to your channel, or open a Jira ticket for every open action — linked back to the meeting.

Connect in about five minutes

Add the TeamRetro MCP server in your assistant, sign in to TeamRetro in the browser, and start asking. The endpoint is the same everywhere:

https://mcp.teamretro.com/mcp

Or follow a step-by-step guide for your assistant:

Set up Claude Set up ChatGPT Set up Microsoft Copilot Set up Gemini

Working in Cursor, Windsurf, Zed or VS Code instead? Add a new MCP server with the URL above and the Streamable HTTP transport, then approve the OAuth sign-in.

What it can do today

Read

  • List teams and members
  • Summarize and compare retrospectives, health checks and estimation sessions
  • List and filter actions
  • Read working agreements
  • Track health-check trends over time

Do

  • Start retros, health checks and planning poker sessions
  • Create and update actions, and park topics
  • Keep working agreements current
  • As yourself, vote and add health-check feedback

Write actions respect your permissions and anonymity settings.

Built on permissions you already trust

Questions, answered

Which AI assistants work with the TeamRetro MCP server?
Any MCP-compatible client — including Claude (web, desktop and Claude Code), ChatGPT, Microsoft Copilot and Gemini, plus editor clients like Cursor, Windsurf, Zed and VS Code. The server speaks Streamable HTTP with OAuth 2.1, so new MCP clients work without any change on our side.
What do I need to connect?
A TeamRetro plan that includes API & MCP access, an MCP-compatible assistant, and account-admin permission to approve a connected app. Setup is a browser sign-in — no API key to copy.
How does sign-in work, and is my data safe?
You connect with OAuth 2.1 and sign in to TeamRetro in your browser. The connection is account-level — one TeamRetro account per connection. Anything the assistant does on your behalf respects your existing permissions and your team's anonymity settings, and you can revoke the connection at any time.
Can the assistant see all of my teams?
On standard plans an assistant reads the teams you're a member of. Cross-team, account-wide insights — "how are all my teams doing?" — are an Enterprise capability. Talk to us about Enterprise.
How is this different from the API?
Same data, different door. The MCP server is for working in natural language from your assistant; the API and webhooks are for building your own integrations and automations. Many teams use both.

Enterprise-grade security, compliance, and control

TeamRetro is SOC 2 Type 2 accredited by an independent auditor who has evaluated our policies, product, platform, and infrastructure in accordance with the Standard on Assurance Engagements (ASAE 3150).

REQUEST SOC 2 VIA TRUST CENTER DOWNLOAD SOC 3
SOC 2 Type 2 SOC 3

  • GDPR compliance and regional hosting (US & EU)

  • Single Sign-On (SSO) via SAML

  • SCIM for scalable user provisioning

  • Audit logs available on request

We maintain 99.9% uptime, with fast-response SLAs to ensure your teams stay productive and supported. Status dashboard