Labsco
MCP SERVER

TeamRetro

by adepanges

Manage TeamRetro from your client — teams, users, actions, agreements, health checks, retrospectives and CSV reports.

Project & Task Management
Summary
The reporting tools are the reason to install it.

CRUD over teams and users is convenient; the seven report tools are the part you cannot easily replicate, because they return TeamRetro's own computed statistics — participation rates, overdue actions bucketed by age, historical health scores per dimension — as CSV a model can summarise directly. Because it tracks the public API, a change on TeamRetro's side can change what these return.

What it is

A community-built server over TeamRetro's public API, covering the platform broadly rather than one corner of it. Alongside CRUD for teams, users and their retrospective artefacts, it exposes TeamRetro's reporting endpoints, which return CSV — that is where the analytical value sits, since those reports are hard to assemble by hand.

What you get
  • Users: `list_users`, `get_user`, `add_user`, `update_user`, `delete_user`, all keyed by email address
  • Teams and members: `list_teams`, `detail_team`, `create_team`, `update_team`, `delete_team`, plus `list_team_members`, `get_team_member`, `add_team_member`, `update_team_member`, `remove_team_member`
  • Actions: `list_actions`, `create_action`, `get_action`, `update_action`, `delete_action` with due date, completion, priority and assignee
  • Agreements: `list_agreements`, `create_agreement`, `get_agreement`, `update_agreement`, `delete_agreement`
  • Health: `list_health_checks`, `get_health_check`, `delete_health_check`, `list_health_models`, `get_health_model`
  • Retrospectives: `list_retrospectives`, `get_retrospective`, `delete_retrospective`
  • Reports as CSV: `team_activity_report`, `team_actions_activity_report` with open/completed/overdue counts by age range, `retrospective_activity_report` and `health_check_activity_report` with participation rates and idea, comment, action and agreement counts, `team_health_latest_report` and `team_health_historical_report` by health model, and `users_report` with roles, memberships and activity
  • Filtering by team tags and team IDs, and offset/limit pagination, on the list endpoints
Requirements

A TeamRetro API key, set as `TEAMRETRO_API_KEY` with `TEAMRETRO_AUTH_TYPE` set to `apiKey`. `TEAMRETRO_BASE_URL` defaults to `https://api.teamretro.com` and only needs setting if yours differs. Run it through `npx` from the published `teamretro-mcp-server` package, install through Smithery, or build from source with `pnpm install` and `pnpm run build`. Package `teamretro-mcp-server`, version 0.12.6. This is a community project, not built or endorsed by TeamRetro.

Setup effort

One command plus a key — npx -y @smithery/cli install @adepanges/teamretro-mcp-server --client claude, then supply credentials