Frequently Asked Questions (FAQ) about TeamRetro MCP Server

Q: What is the TeamRetro MCP Server? A: The TeamRetro MCP Server is a Model Context Protocol (MCP) server that allows AI agents within the UBOS ecosystem to interact with TeamRetro, a platform for agile retrospectives. It provides a standardized interface for accessing and manipulating TeamRetro data.

Q: Is this an official TeamRetro integration? A: No, this MCP server is an unofficial, community-developed interface. It leverages TeamRetro’s public API but is not developed or endorsed by TeamRetro.

Q: What functionalities does the TeamRetro MCP Server provide? A: The server provides tools for managing users, teams, team members, actions, agreements, health checks, health models, and retrospectives within TeamRetro.

Q: How do I install the TeamRetro MCP Server? A: You can install it using NPX (recommended for easy setup) or by cloning the repository from source code, installing dependencies, and building the project.

Q: What environment variables do I need to configure? A: You need to configure the TeamRetro API key (TEAMRETRO_API_KEY) and optionally the TeamRetro base URL (TEAMRETRO_BASE_URL). The authentication type also needs to be set to apiKey via TEAMRETRO_AUTH_TYPE.

Q: How can AI agents benefit from this integration? A: AI agents can automate retrospective analysis, manage action items, monitor team health, provide personalized recommendations, and streamline user and team management.

Q: Where can I find the API documentation for TeamRetro? A: The API documentation is available at: https://help.teamretro.com/article/320-teamretro-api and https://groupmap.stoplight.io/docs/teamretro/.

Q: What is UBOS, and how does it relate to the TeamRetro MCP Server? A: UBOS is a full-stack AI agent development platform that simplifies the process of orchestrating AI agents, connecting them with enterprise data, and building custom AI agents. The TeamRetro MCP Server is an asset in the UBOS marketplace that allows AI agents built on UBOS to interact with TeamRetro.

Q: What if the TeamRetro API changes? A: Since the MCP server connects directly to TeamRetro’s official API, any changes to the TeamRetro API may affect the MCP server’s functionality. Updates to the MCP server will be made to maintain compatibility.

Q: Can I contribute to the development of the TeamRetro MCP Server? A: Yes, as a community-developed project, contributions are welcome. Please refer to the repository for contribution guidelines.