The retro tool with an MCP server for AI agents
Looptro is a retrospective tool you shape to fit how your team works, and it ships a Model Context Protocol (MCP) server so AI agents like Claude Code, Cursor, and your own custom agents can join your retros as first-class participants. Point an agent at Looptro and it can read past retros, prep the board before a session, and follow up on the action items a retro produces, all through capability-scoped, revocable, team-scoped tokens with a full audit trail.
What your agents can do
Looptro's MCP tools cover the whole retro workflow: prep, the retro itself, and follow-up. What an agent can actually do is bounded by the scopes you approve when you connect it.
Read past retros
With the retros:read
scope an agent can list your team's retros, fetch a single retro's
full board (columns, posts, and action items in one call), and read
the summary narrative. That's the context an agent needs to spot
recurring themes before anyone opens the board.
Prep the board
With write scopes an agent can create a retro from a template, seed context posts, group and rename related cards, mark itself ready, and set the summary narrative. It sets the sprint cycle so the next retro lands in the right place. The team walks into a board that already has the groundwork done.
Follow up on carry-forward action items
Action items are first-class objects that carry forward to the next retro. An agent can read the open items, update their status as work lands, and file new ones, so the commitments a retro produces actually get chased between sessions instead of going stale.
The full tool and scope table lives in the MCP docs.
How agent access is secured
An agent token, whether issued through the OAuth flow or minted by hand, carries only the access you grant and nothing more.
- Capability-scoped. A token carries only the scopes you approved. A tool call missing its required scope is refused with a 403 that names the scope, so an agent can never quietly do more than you allowed.
- Team-scoped. One token, one team. Multi-team agents install once per team, which keeps the audit trail clean.
- Revocable. Every token lives in team settings with a management UI. Revoke one and it stops working immediately.
- Bounded expiry. Tokens last up to 365 days, and you can pick the exact expiry when you mint one by hand, so access lapses on its own even if you forget.
- Rate-limited. Agents get a stricter per-token budget than human sessions, with 429 back-pressure instead of silent failure.
- Audit trail. Every tool call writes an audit row tagged as an agent action, with the token, the issuing user, the team, and any error. Agent actions sit alongside human actions in the same timeline.
How to connect an agent
The MCP server is at
https://app.looptro.dev/mcp
on the same host as the app. In Claude Code, one command adds it:
claude mcp add looptro --url https://app.looptro.dev/mcpClaude Code runs the OAuth handshake for you. The first call opens a consent page where you pick the team and approve the scopes the agent is asking for. Three paths cover every environment:
- Browser agents approve scopes on the consent page via a standard OAuth 2.0 flow with auto-discovery.
- Headless agents (CLI, cron, a container with no browser) fall back to the device-code flow: the agent prints a short code, you approve it on any device, and it picks up the token.
- Scripts that cannot do OAuth use a personal access token minted from team settings and sent as a bearer token. Same audit attribution as the OAuth path.
The step-by-step install, the OAuth discovery detail, and the full tool reference are in the MCP docs.
An example workflow
Say your team runs a retro every second Friday and you want your agent to take the prep off your plate:
- The day before, the agent reads last sprint's retro and its summary, then pulls the action items that carried forward and checks which ones actually shipped.
- It creates Friday's retro from your team's template and seeds a few context posts: the carry-forward items still open, and any recurring theme it noticed across the last few retros.
- It sets the summary narrative with a short "here's where we left off" note, so the team opens a board that already has the thread of the last few sprints.
- The team runs the retro through Reflect, Group, Vote, and Discuss. This is the part humans do; the agent stays out of the conversation.
- Afterward, the agent files the new action items the discussion produced and updates the status of the ones the team closed, ready to carry forward into the next retro.
Every one of those calls is scoped to what you approved and logged as an agent action, so you always know exactly what the agent touched.
Works with export and the REST API
MCP is the right surface for AI agents that need capability-scoped tool calls and an audit trail. It sits next to two other shipped connections:
- Data export. Pro and Maxx teams export any retro, with posts, groupings, votes, and action items, as Markdown or JSON from team settings.
- REST API. A typed REST surface, described by OpenAPI, for everything that is not an agent: dashboards, custom integrations, or a bot. See the REST API docs.
Native integrations with Linear, Jira, GitHub, GitLab, Slack, Microsoft Teams, and Notion are coming. Today, an agent over MCP or the REST API is how you wire that context in.
Questions about AI agents and MCP
-
Which AI agents work with Looptro?
- Any agent that speaks the Model Context Protocol. Claude Code and Cursor connect out of the box, and custom agents work too because the server is standard JSON-RPC 2.0 over HTTP with OAuth 2.0 auto-discovery. If your agent can add an MCP server by URL, it can join a Looptro retro.
-
Is the MCP server free?
- MCP access is included on the Pro and Maxx plans. The free anonymous tier runs full retros with no signup, but it does not expose the API, MCP server, audit log, or data export, so you need a Pro or Maxx team to connect an agent.
-
Can an agent change or delete my retros?
- Only within the scopes you approve. Tokens are capability-scoped: grant read-only scopes and the agent can look but not touch; grant write scopes and it can create retros, add posts, and file action items. Any tool call missing its scope is refused with a 403, every call is written to the audit log tagged as an agent action, and you can revoke a token at any time from team settings.
-
Do I need an account to connect an agent?
- Yes. MCP access lives on the Pro and Maxx plans, which are account-based. Anonymous free-tier retros are ephemeral and do not expose an API or MCP server, so there is nothing for an agent to connect to.
-
Can an AI agent run a retro on its own, without the team?
- It can, but that is not what Looptro is for. Agents prepare the ground, surface patterns from past retros, and follow up on action items so the team spends its retro time on the conversation. The humans still run the retro.
-
How do I revoke an agent's access?
- Delete the token. Every agent token, whether minted through the OAuth flow or by hand, lives in team settings with a management UI, and revoking it takes effect immediately. Tokens also carry a bounded expiry of up to 365 days, so access lapses on its own if you forget.
Bring your agent to the retro
Connect Claude Code, Cursor, or your own agent over MCP and let it do the prep and the follow-up.