A
licenseA
qualityC
maintenanceGenerates engineering intelligence reports (standups, weekly summaries, sprint retrospectives) from GitHub and Jira data, accessible via MCP clients or CLI.
10
4 npm
MIT
retro-mcp
Related Servers
Alternatives to retro-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceSummarizes Slack activity and GitLab merge requests with OpenAI to help generate daily standups, weekly reports, or quarterly check-ins.-
- AlicenseAqualityDmaintenanceGenerates daily standup drafts from your actual GitHub, Jira, Linear, and Slack activity, grouping work items and detecting blockers.524 npmMIT
- FlicenseBqualityNot gradedmaintenanceGenerates AI-powered daily and weekly productivity summaries by analyzing your Slack messages, Google Calendar events, and Gmail activity with automated scheduling and smart filtering.6-
- AlicenseBqualityCmaintenanceAnalyzes git repository metrics to understand team health, development patterns, code quality, and collaboration through natural language queries. Provides insights on commit statistics, bus factor, velocity trends, technical debt, and burnout detection.126 npm1MIT
- FlicenseAqualityCmaintenanceProvides sprint and developer analytics from Jira, answering questions about sprint content, developer performance, and refinement readiness. Can publish reports to Confluence for easy sharing.7-
TDQS
A4.2/5.0
Scored across 6 tools
Disambiguation5/5
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.
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness5/5
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.
Maintenance
ActivityInactive
ResponsivenessNo issues