Skip to main content
Glama
Sign In
retro-mcp

retro-mcp

by sathvic-kollu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to retro-mcp

No user-submitted related servers found.

    Related Servers

    • Prodbeam MCP Server

      prodbeam
      A
      license
      A
      quality
      C
      maintenance
      Generates engineering intelligence reports (standups, weekly summaries, sprint retrospectives) from GitHub and Jira data, accessible via MCP clients or CLI.
      10
      4 npm
      MIT

    • quality-kpi-mcp

      Misfit1982
      A
      license
      A
      quality
      C
      maintenance
      Enables engineering leaders to query their AI assistant for quality KPIs — MTTR, MTTA, DORA metrics, defect escape rate and SLA breaches — computed from Jira bug, incident and deployment CSV exports already on hand. It delivers trends, period comparisons, hotspot findings and ready-to-share executive summaries and HTML dashboards without a BI stack or data warehouse.
      10
      MIT

    • Git Metrics MCP Server

      jonmatum
      A
      license
      B
      quality
      C
      maintenance
      Analyzes 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.
      12
      13 npm
      1
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    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

    Resources