Key features: - Complete TeamRetro API coverage with 20+ tools for managing teams, users, actions, and more - Simplified AI client integration through standardized MCP interfaces - Built-in pagination and filtering…
teamretro-mcp-server source profile. From the maintainer documentation: “Key features: - Complete TeamRetro API coverage with 20+ tools for managing teams, users, actions, and more - Simplified AI client integration through standardized MCP interfaces - Built-in pagination and filtering support for efficient data handling - Secure API authentication handling and environment configuration - Comprehensive documentation and easy setup options”
The documented npm package is teamretro-mcp-server. The configuration below comes from the maintainer’s example; adapt its paths and account values to your environment.
The example declares TEAMRETRO_AUTH_TYPE, TEAMRETRO_API_KEY. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| list_users | List users with pagination using offset and limit parameters to control the number of results returned |
| add_user | Add a new user or update an existing user's information by their email address, specifying optional name and emailAddress |
| update_user | Update an existing user's details, such as their name and emailAddress, by providing their current email |
| delete_user | Delete a user by their email address |
| get_user | Retrieve detailed information about a single user by their email address |
| list_teams | List teams from TeamRetro with filtering by tags and IDs, and pagination using offset and limit parameters |
| detail_team | Retrieve detailed information about a single team by its unique ID |
| update_team | Update an existing team's details, such as its name and associated tags, by providing the team's ID |
| create_team | Create a new team with a required name, and optional tags and members |
| delete_team | Delete an existing team by its ID |
| list_team_members | Retrieve a list of team members for a specified team ID with pagination controls for offset and limit |
| get_team_member | Fetch a team member by their email address within a specified team |
| update_team_member | Update a team member's details, such as their name or team admin status, by their email address within a specified team |
| remove_team_member | Remove a team member from a team by their email address |
| add_team_member | Add a new team member to a team by their email address, with optional specification of team admin status |
| list_actions | Retrieve a list of actions from TeamRetro with optional filtering by team tags and team IDs, and pagination controls for offset and limit |
| create_action | Create a new action in TeamRetro with required details such as team ID, title, due date, completion status, and assigned user |
| get_action | Fetch a single action by its unique ID from TeamRetro |
| update_action | Update an existing action in TeamRetro with new details such as title, due date, completion status, priority, and assigned user |
| delete_action | Delete an existing action from TeamRetro by its action ID |
| list_agreements | List agreements from TeamRetro with optional filtering by team tags and team IDs, as well as pagination controls |
| create_agreement | Create a new agreement in TeamRetro by specifying the team it belongs to and its title |
| get_agreement | Retrieve a single agreement by its unique identifier |
| update_agreement | Update an existing agreement's details such as its title or associated team |
| delete_agreement | Delete an existing agreement by specifying its unique identifier |
| list_health_checks | List health checks from TeamRetro with optional filtering by health model IDs, team tags, and team IDs, as well as pagination controls |
| get_health_check | Retrieve a single health check by its unique identifier with optional attributes to include |
| delete_health_check | Delete an existing health check by specifying its unique identifier |
| list_health_models | List health models from TeamRetro with pagination controls |
| get_health_model | Retrieve a single health model by its unique identifier |
| list_retrospectives | List retrospectives from TeamRetro with filtering by team tags and IDs, and pagination using offset and limit parameters |
| get_retrospective | Retrieve detailed information about a single retrospective by its unique ID |
| delete_retrospective | Delete an existing retrospective by its ID |
| team_activity_report | Generate a team activity report from TeamRetro with filtering by team tags and team IDs |
| team_actions_activity_report | Generate a team actions activity report from TeamRetro with filtering by team tags and team IDs. Returns CSV data with action statistics including open… |
| retrospective_activity_report | Generate a retrospective activity report from TeamRetro with filtering by date range, team tags and team IDs. Returns CSV data with retrospective statistics… |
| health_check_activity_report | Generate a health check activity report from TeamRetro with filtering by date range, team tags and team IDs. Returns CSV data with health check statistics… |
| team_health_latest_report | Generate a team health (latest) report from TeamRetro for a specific health model with filtering by date range, team tags and team IDs. Returns CSV data with… |
| team_health_historical_report | Generate a team health (historical) report from TeamRetro for a specific health model with filtering by date range, team tags and team IDs. Returns CSV data… |
| users_report | Generate a users report from TeamRetro with filtering by team tags and team IDs. Returns CSV data with user information including account roles, team… |
{
"mcpServers": {
"teamretro-mcp-server": {
"command": "npx",
"args": [
"-y",
"teamretro-mcp-server"
],
"env": {
"TEAMRETRO_AUTH_TYPE": "apiKey",
"TEAMRETRO_API_KEY": "YOUR_TEAMRETRO_API_KEY"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| TEAMRETRO_AUTH_TYPE | Declared in the maintainer’s client configuration. | Check documentation |
| TEAMRETRO_API_KEY | Declared in the maintainer’s client configuration. | Check documentation |
메모짱 메모·할 일을 AI로 검색·정리·체크해요. / Search, write and check off notes and to-dos in Memozzang.
채팅으로 후잉 가계부를 관리하세요. 거래 입력·조회, 계정·예산 관리, 손익·재무 보고서를 지원합니다.
나라장터 낙찰정보서비스 Open API를 위한 로컬 MCP 서버
나라장터 사전규격정보서비스 Open API를 위한 로컬 MCP 서버
나라장터 입찰공고정보서비스(공공데이터포털 data.go.kr) Open API를 감싼 로컬 MCP 서버
나라장터 사용자정보서비스(공공데이터포털 data.go.kr) Open API를 감싼 로컬 MCP 서버