MCP server · For AI tools
Your retros, open to your AI tools
Free for one team · MCP is included on every plan
Ask your AI tool
What did we agree on in the last retro?
Sprint 14 has 2 open action items:
1. Give staging an owner and an alert (Priya)
2. Tag stories with estimates (Marcus)
An example of what you can ask once the tool is connected. The answers come from your own retros.
What the MCP server lets an AI tool do
Read your retros
List your teams, Team Rooms and retros, and read a retro’s board: every column, the notes in it, and the action items.
Add notes and action items
Drop a note into a column, or add an action item and assign it to a teammate. It shows up on the board right away, like any other note.
As you, with a key you control
Each person creates their own API key. It reaches only the teams that person is on, and it can be revoked at any time.
How to create a key and connect a tool
- 1
Sign in and open Integrations
Integrations is in the dashboard sidebar. You need a Retro Rabbit account with a verified email address; people who joined a retro as a guest can’t create keys.
- 2
Create an API key
Under AI tools, name the key after where you’ll use it, for example “Claude Code on my laptop”, and press Create key. The name is how you’ll know which key to revoke later.
- 3
Copy the key straight away
The key starts with rr_ and is shown once. Retro Rabbit keeps only a hash of it, so it can’t show it to you again.
- 4
Add the server to your AI tool
Point the tool at https://api.retrorabbit.io/mcp and send the key in an Authorization header, as a Bearer token. The set-up for Claude Code and for Cursor is on this page.
- 5
Ask it something
Try “What did we agree on in the last retro?” The tool looks up your teams, rooms and retros itself, then answers from the notes and action items.
Server details
- URL
- https://api.retrorabbit.io/mcp
- Header
- Authorization: Bearer rr_your_key
- Transport
- Streamable HTTP. Each request is one JSON-RPC message with a JSON reply.
- Protocol versions
- 2025-11-25, 2025-06-18 and 2025-03-26
Claude Code
Run this in a terminal, with your own key in place of rr_your_key. The Integrations page shows the same command with your key already in it.
claude mcp add --transport http retrorabbit \
https://api.retrorabbit.io/mcp \
--header "Authorization: Bearer rr_your_key"Cursor
Add this to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project, and set RETRORABBIT_API_KEY in your environment to your key.
{
"mcpServers": {
"retrorabbit": {
"url": "https://api.retrorabbit.io/mcp",
"headers": {
"Authorization": "Bearer ${env:RETRORABBIT_API_KEY}"
}
}
}
}Other tools
Add a remote (HTTP) MCP server in the tool’s settings with the URL and the header above. To check a key before you configure anything, ask the server for its list of tools:
curl -s https://api.retrorabbit.io/mcp \
-H "Authorization: Bearer rr_your_key" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'The tools, with an example for each
| Tool | What it does | Something you might ask |
|---|---|---|
| list_teams | The teams you’re on, with their IDs. | “Which Retro Rabbit teams am I on?” |
| list_rooms | A team’s retro rooms, with their IDs and current retros. | “Which Team Rooms does my team have?” |
| list_retros | One room’s retros, with their IDs and action items. | “List the retros in the Platform room.” |
| get_notes | A retro’s board: its columns and the notes in each, plus action items. | “What did people write in the Sprint 14 retro?” |
| add_note | Adds a note to a column of a retro, as you. | “Add a note under “Didn’t go well”: checkout tests timed out again.” |
| add_action_item | Adds an action item to a retro, optionally assigned to a teammate. | “Add an action item: give staging an owner and an alert.” |
| my_action_items | Your action items across the team’s rooms. | “Which action items do I still owe?” |
| room_action_items | Every action item in one room, by retro. | “Show every action item in the Platform room.” |
Security notes
- Your access only
- A key belongs to one person. It reaches the teams that person is on and nothing else, with the same team checks as the web app.
- Shown once
- The key is displayed when you create it and never again. Retro Rabbit stores only a SHA-256 hash of it.
- Revocable
- Revoke a key on the Integrations page and it stops working right away. Each key shows when it was last used, and you can have up to 20 at a time.
- MCP only
- A key works on the MCP endpoint and nowhere else. It can’t sign in to the web app, create other keys or touch billing.
- Read and add
- The tools read retros and add notes and action items. There are no tools that edit or delete.
- Your AI tool
- Whatever the tool reads from your retros is handled by that tool and its AI provider, under their terms. Connect only tools you trust with your team’s notes.
Limits, stated plainly
API keys, not OAuth. Tools that can only connect through an OAuth sign-in, such as connectors in the Claude and ChatGPT apps, can’t use it yet.
It answers; it doesn’t push. There is no event stream, so a tool isn’t told when a board changes. It sees the current state each time it asks.
Eight tools. An AI tool can’t vote, edit or delete notes, complete action items, start a retro, or send an action item to Jira or Linear.
Personal keys only. There are no team-wide or organization-wide keys, and guests can’t create one.
Frequently asked questions
What is the Retro Rabbit MCP server?
It’s an endpoint that speaks the Model Context Protocol (MCP), the standard AI tools use to reach outside systems. With it, an AI tool can list your retros, read the notes, and add notes and action items in Retro Rabbit, acting as you.
Which AI tools can connect?
Tools that can connect to a remote MCP server over HTTP and send an Authorization header, such as Claude Code and Cursor. This page has the set-up for both. Tools that can only connect through an OAuth sign-in, such as connectors in the Claude and ChatGPT apps, aren’t supported yet.
Is the MCP server free?
Yes. API keys and the MCP server are available on every plan, including the free plan for one team.
Can an AI tool change or delete things in our retros?
It can add notes and action items. It can’t edit or delete notes, vote, complete action items or start a retro: the server has no tools for those.
Whose access does the AI tool have?
Yours. A key belongs to one person and reaches only the teams that person is on, with the same checks as the web app. Notes it adds are added as you. There are no team-wide keys.
How do I revoke a key?
On the Integrations page, press Revoke next to the key. Anything using it stops working right away. The page also shows when each key was last used.
What happens to the notes my AI tool reads?
They go to the tool you connected, which handles them under its own terms. The MCP server only answers requests made with your key; it doesn’t push data anywhere. Connect only tools you trust with your team’s retro notes.
More integrations
All integrations- JiraSend a retro action item to a Jira project as an issue. Its key and status show back on the action.How it works
- LinearSend a retro action item to a Linear team as an issue. The issue and its status show back on the action.How it works
- SlackAdd a retro note without leaving Slack with /retro, and get reminders to add notes where your team already talks.How it works
Give your AI tools something real to work with.
Start with one team for free, run a retro, then create a key on the Integrations page and ask about it.
Free for one team · No credit card