# Retro Meeting — REST API endpoint `retro-meeting`

Turn a finished sprint-retrospective board into shareable results: a Markdown summary grouped by category with items sorted by votes, a CSV export, and stats (item counts, revealed count, participants, counts per category, top-5 voted items). Supports the page's formats — standard (went well / needs improvement / action items), sailboat, 4Ls, start-stop-continue — or a custom list of categories. Hidden (unrevealed) items stay out of the exports, as on the page.

- Category: productivity
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/retro-meeting/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/retro-meeting/
- Same tool on the other surface: https://findutils.com/mcp/retro-meeting/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/retro-meeting/execute \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Sprint 42",
    "date": "2026-08-14",
    "items": [
      {
        "category": "went_well",
        "text": "Release on time",
        "votes": 5
      }
    ]
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/retro-meeting
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Retrospective / sprint name used in the title. |
| `format` | string (standard \| sailboat \| 4ls \| start_stop \| custom) | no | Board format. Default "standard". Use "custom" with your own categories. Default: `"standard"`. |
| `categories` | array | no | Category names for format "custom" (1-12). Ignored for the built-in formats. |
| `items` | array | no | Board items: { category, text, author, votes (default 0), revealed (default true) }. category must be a category id of the format (e.g. "went_well") or, for custom, one of your category names. |
| `anonymous` | boolean | no | Print "Anonymous" instead of authors. Default true, as on the page. Default: `true`. |
| `date` | string | no | Session date, YYYY-MM-DD. Default: today (UTC). |

Example arguments (verified):

```json
{
  "name": "Sprint 42",
  "date": "2026-08-14",
  "items": [
    {
      "category": "went_well",
      "text": "Release on time",
      "votes": 5
    }
  ]
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:retro_meeting`. Full MCP reference: https://findutils.com/mcp/retro-meeting/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt