retro-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Your Jira account email (required for live mode) | |
| SLACK_TOKEN | No | Slack read token to scan for blocker and incident language | |
| GITHUB_REPOS | No | Comma-separated list of GitHub repos (owner/name) | |
| GITHUB_TOKEN | No | GitHub read-only token for PR review latency and reverts | |
| JIRA_BASE_URL | Yes | Your Jira Cloud base URL (required for live mode) | |
| JIRA_BOARD_ID | No | Optional Jira board ID to pin when account has several | |
| JIRA_API_TOKEN | Yes | Your Jira API token (required for live mode) | |
| SLACK_CHANNELS | No | Comma-separated Slack channel IDs |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| retro_briefA | Generate a data-grounded sprint retrospective for the most recently closed sprint: What went well, What did not, Action items, and Discussion prompts. Every line is backed by a metric, ticket, PR, or Slack thread, framed around the process not individuals. Recurring themes across recent sprints are flagged. |
| retro_metricsA | The hard numbers behind the retro for the closed sprint: completion, mid-sprint scope change, carryover, reopens, average cycle time vs the prior sprint, velocity, PR review latency, reverts and hotfixes, and flagged Slack threads. This is the evidence base the brief draws from. |
| discussion_promptsA | Open questions for the retro board, each grounded in a real anomaly from the closed sprint (a reopened ticket, mid-sprint scope, a slow review, a revert, a blocker). Questions to start the conversation, not verdicts that end it. |
| action_item_reviewA | Close the loop on last retro's action items. Give the previous retro's action items and it attaches THIS sprint's relevant data to each, so the team can see what actually moved. Reviewing prior actions is the single proven lever on retro follow-through. It shows evidence only and lets you judge what counts as done. |
| sprint_compareA | Compare the closed sprint against the one before it (completion, scope, carryover, reopens, cycle time, velocity), and list the problem themes that recur across recent sprints. Use it to tell a one-off from a pattern. |
| list_sourcesA | Show which data sources are configured (Jira, plus optional GitHub and Slack enrichment), or that the server is running on a synthetic demo sprint. Does not hit the network; run the server with --check to verify live connections. |
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 6 tools
Each tool targets a distinct aspect of the retrospective workflow: raw metrics, generated brief, discussion prompts, action item follow-up, sprint comparison, and source configuration. There is no overlap or ambiguity between tool purposes.
All names use snake_case and most follow a noun_verb or noun_noun pattern with a clear domain prefix (retro_, discussion_, action_item_, sprint_). 'list_sources' uses a verb_noun pattern, which is a minor deviation but still readable and consistent in style.
Six tools is well within the ideal range for a domain-specific server. Each tool addresses a necessary part of the retrospective process, and none are redundant or superfluous.
The tool surface covers the full retrospective lifecycle: generate evidence-based insights, produce a summary brief, prompt discussion, review prior action items, and compare sprints. Optional source listing rounds out the set without any obvious gaps.