quality-kpi-mcp
Related Servers
Alternatives to quality-kpi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceTurns JUnit XML test reports from CI into queryable QA metrics, letting AI assistants answer plain-English questions about failures, flaky tests, regressions pinned to a commit, root-cause clusters, and performance drift. Also generates ready-to-share QA health reports and self-contained HTML dashboards without logging into separate tools.11MIT
- FlicenseNot gradedqualityDmaintenanceEnables intelligent analysis of regression test failures and automatic discovery of solutions in JIRA. Analyzes test logs using AI-driven algorithms and matches errors with relevant JIRA issues through natural language interactions.-
- AlicenseNot gradedqualityDmaintenanceConnect engineering metrics, DORA performance, deploy risk scoring, and PR health to any AI assistant. Score PRs for deployment risk using a 36-signal model, query team health, incidents, coverage, and more.MIT
- AlicenseAqualityDmaintenanceGenerates sprint retrospectives grounded in actual data from Jira, GitHub, and Slack, providing evidence-backed insights and action items.685 npmMIT
- AlicenseBqualityBmaintenanceEnables AI clients to analyze software test results and defect records, producing explainable GO, CONDITIONAL_GO, or NO_GO release-readiness recommendations with deterministic risk scoring, failed-test retrieval, defect hotspot ranking, and regression test planning.4MIT
- FlicenseNot gradedqualityBmaintenanceEnables natural-language Q&A over customer support ticket data. Provides tools for schema inspection, SQL-based ticket counts and grouping, and full-text search for customer wording without requiring API keys.-
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: data inventory, defect aging, defect metrics, incident MTTR, DORA metrics, change-failure breakdown, KPI trends, period comparison, executive summary, and dashboard export. Overlaps such as time-to-restore appearing in both MTTR and DORA tools are framed at different levels of aggregation, and the descriptions make the boundaries clear.
All tools use consistent snake_case with a clear verb_noun pattern: get_, list_, compare_, generate_, and export_. The naming is predictable and readable throughout, including acronym cases like get_mttr and get_dora_metrics.
Ten tools is well-scoped for a quality KPI reporting server, with separate tools for each major metric family, reporting workflow, and data discovery need. No tool appears redundant or purely decorative.
The surface covers the domain end to end: discovering loaded data, retrieving defect, incident, DORA, and change-failure metrics, trending and comparing KPIs, and producing executive-level summaries and dashboards. No obvious operational gap would block the intended reporting workflows.