by adepanges
Connect to TeamRetro for seamless team collaboration and task management. Enhance your workflow with leading project mgm
Connects to TeamRetro's team management platform to create and manage teams, users, and members through natural language commands.
TeamRetro is a community-built MCP server published by adepanges that provides AI assistants with tools and capabilities via the Model Context Protocol. Connect to TeamRetro for seamless team collaboration and task management. Enhance your workflow with leading project mgm It is categorized under productivity.
You can install TeamRetro in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
Apache-2.0
TeamRetro is released under the Apache-2.0 license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
TeamRetro is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
TeamRetro has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
I recommend TeamRetro for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
TeamRetro is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend TeamRetro for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
According to our notes, TeamRetro benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
I recommend TeamRetro for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
TeamRetro has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, TeamRetro benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
TeamRetro reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
showing 1-10 of 38
<a href="https://smithery.ai/server/@adepanges/teamretro-mcp-server"><img alt="Smithery Badge" src="https://smithery.ai/badge/@adepanges/teamretro-mcp-server"></a>
A Model Context Protocol (MCP) server that provides AI-powered integration with TeamRetro's platform. This server acts as a bridge between AI clients and TeamRetro's official API, enabling seamless interaction with team management, retrospectives, health checks, and other TeamRetro features through standardized MCP tools.
Key features:
Whether you're building AI-powered team analytics, automated retrospective management, or integrating TeamRetro into your AI workflow, this MCP server provides the foundation you need.
This MCP server is an unofficial community-developed interface to TeamRetro's services. While not developed or endorsed by TeamRetro, it provides standardized access to their platform.
The server connects directly to TeamRetro's official public API:
All API endpoints and functionality are based on TeamRetro's official documentation:
{
"mcpServers": {
"teamretro-mcp-server": {
"command": "npx",
"args": ["-y", "teamretro-mcp-server"],
"env": {
"TEAMRETRO_AUTH_TYPE": "apiKey",
"TEAMRETRO_API_KEY": "your-api-key"
}
}
}
}
To install TeamRetro MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @adepanges/teamretro-mcp-server --client claude
git clone https://github.com/adepanges/teamretro-mcp-server.git
cd teamretro-mcp-server
pnpm install
pnpm run build
{
"mcpServers": {
"teamretro-mcp-server": {
"command": "node",
"args": ["/path/to/teamretro-mcp-server/dist/index.js"],
"env": {
"TEAMRETRO_AUTH_TYPE": "apiKey",
"TEAMRETRO_API_KEY": "your-api-key"
}
}
}
}
.env.example to .env and modifying it according to your needs.pnpm run inspector
The base URL for the TeamRetro API can be set using the TEAMRETRO_BASE_URL environment variable. By default, it is set to https://api.teamretro.com.
{
"env": {
"TEAMRETRO_BASE_URL": "https://api.teamretro.com"
}
}
{
"env": {
"TEAMRETRO_AUTH_TYPE": "apiKey",
"TEAMRETRO_API_KEY": "your-api-key"
}
}
The server provides the following tools:
list_users: List users with pagination using offset and limit parameters to control the number of results returnedadd_user: Add a new user or update an existing user's information by their email address, specifying optional name and emailAddressupdate_user: Update an existing user's details, such as their name and emailAddress, by providing their current emaildelete_user: Delete a user by their email addressget_user: Retrieve detailed information about a single user by their email addresslist_teams: List teams from TeamRetro with filtering by tags and IDs, and pagination using offset and limit parametersdetail_team: Retrieve detailed information about a single team by its unique IDupdate_team: Update an existing team's details, such as its name and associated tags, by providing the team's IDcreate_team: Create a new team with a required name, and optional tags and membersdelete_team: Delete an existing team by its IDlist_team_members: Retrieve a list of team members for a specified team ID with pagination controls for offset and limitget_team_member: Fetch a team member by their email address within a specified teamupdate_team_member: Update a team member's details, such as their name or team admin status, by their email address within a specified teamremove_team_member: Remove a team member from a team by their email addressadd_team_member: Add a new team member to a team by their email address, with optional specification of team admin statuslist_actions: Retrieve a list of actions from TeamRetro with optional filtering by team tags and team IDs, and pagination controls for offset and limitcreate_action: Create a new action in TeamRetro with required details such as team ID, title, due date, completion status, and assigned userget_action: Fetch a single action by its unique ID from TeamRetroupdate_action: Update an existing action in TeamRetro with new details such as title, due date, completion status, priority, and assigned userdelete_action: Delete an existing action from TeamRetro by its action IDlist_agreements: List agreements from TeamRetro with optional filtering by team tags and team IDs, as well as pagination controlscreate_agreement: Create a new agreement in TeamRetro by specifying the team it belongs to and its titleget_agreement: Retrieve a single agreement by its unique identifierupdate_agreement: Update an existing agreement's details such as its title or associated teamdelete_agreement: Delete an existing agreement by specifying its unique identifierlist_health_checks: List health checks from TeamRetro with optional filtering by health model IDs, team tags, and team IDs, as well as pagination controlsget_health_check: Retrieve a single health check by its unique identifier with optional attributes to includedelete_health_check: Delete an existing health check by specifying its unique identifierlist_health_models: List health models from TeamRetro with pagination controlsget_health_model: Retrieve a single health model by its unique identifierlist_retrospectives: List retrospectives from TeamRetro with filtering by team tags and IDs, and pagination using offset and limit parametersget_retrospective: Retrieve detailed information about a single retrospective by its unique IDdelete_retrospective: Delete an existing retrospective by its IDteam_activity_report: Generate a team activity report from TeamRetro with filtering by team tags and team IDsteam_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, completed, and overdue action counts grouped by age rangesretrospective_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 including participation rate, idea count, comment count, action count, and agreement counthealth_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 including participation rate, comment count, action count, and agreement countteam_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 latest team health scores including healPrerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.