MCP Server for TeamRetro integration, providing API services and tools for team management and analytics
Teamretro MCP server exists for a simple reason — assistants are far more useful when they can act on Teamretro directly instead of describing what you should do. MCP Server for TeamRetro integration, providing API services and tools for team management and analytics.
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
Once Teamretro is connected, these are the calls the assistant has available:
Users — The Users tool exposed by this serverTeams — The Teams tool exposed by this serverActions — The Actions tool exposed by this serverAgreements — The Agreements tool exposed by this serverRetrospectives — The Retrospectives tool exposed by this serverReports — The Reports tool exposed by this serverYou will need 3 environment variables: TEAMRETRO_AUTH_TYPE, TEAMRETRO_API_KEY, TEAMRETRO_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Teamretro's toolset — Users, Teams, Actions and 3 more — is a fair guide to whether it matches your workflow. It is maintained by adepanges; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Users | The Users tool exposed by this server. |
| Teams | The Teams tool exposed by this server. |
| Actions | The Actions tool exposed by this server. |
| Agreements | The Agreements tool exposed by this server. |
| Retrospectives | The Retrospectives tool exposed by this server. |
| Reports | The Reports tool exposed by this server. |
{
"mcpServers": {
"teamretro-mcp-server": {
"command": "npx",
"args": ["-y", "teamretro-mcp-server"],
"env": {
"TEAMRETRO_AUTH_TYPE": "apiKey",
"TEAMRETRO_API_KEY": "your-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TEAMRETRO_AUTH_TYPE | Configuration value read at startup. | Optional |
| TEAMRETRO_API_KEY | Credential the server authenticates with. | Yes |
| TEAMRETRO_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.