TeamRetro MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEAMRETRO_TOKEN | No | Your TeamRetro bearer token for bearer authentication | |
| TEAMRETRO_API_KEY | No | Your TeamRetro API key for apiKey authentication | |
| TEAMRETRO_BASE_URL | No | Base URL for TeamRetro API | https://api.teamretro.com |
| TEAMRETRO_PASSWORD | No | Your TeamRetro password for basic authentication | |
| TEAMRETRO_USERNAME | No | Your TeamRetro username for basic authentication | |
| TEAMRETRO_AUTH_TYPE | No | Authentication type (apiKey, basic, or bearer) | apiKey |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_teamsB | List teams from TeamRetro with filtering and pagination |
| detail_teamB | Get a single team by ID |
| update_teamC | Update an existing team |
| create_teamC | Create a new team with optional members and tags |
| delete_teamC | Delete an existing team |
| list_usersC | List users with pagination |
| add_userC | Add or update a user by email |
| update_userC | Update an existing user's information |
| delete_userC | Delete a user by email |
| get_userC | Get a single user by email |
| list_team_membersC | List team members with pagination |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Every tool has a clearly distinct purpose targeting specific resources and actions, with no ambiguity. For example, add_user vs. update_user are differentiated by create/update semantics, and list_team_members is distinct from list_teams in scope. The descriptions reinforce these distinctions, making misselection unlikely.
All tools follow a consistent verb_noun pattern using snake_case, such as create_team, update_user, and list_teams. This predictability aids agent understanding and tool selection, with no deviations in naming conventions across the set.
With 11 tools, the count is well-scoped for managing teams and users in a TeamRetro domain. Each tool earns its place by covering essential operations like CRUD for both resources, plus specific actions like listing members, without being excessive or sparse.
The tool set provides complete CRUD and lifecycle coverage for teams and users, including create, read, update, delete, and list operations. There are no obvious gaps, such as missing pagination or filtering, and agents can handle typical workflows without dead ends.