A
licenseC
qualityC
maintenanceEnables AI-powered automated testing, security scanning, code review, and maintenance tasks directly within Claude Code or desktop.
12
4
MIT
Test Reporter MCP Server
by WillBrock
Related Servers
Alternatives to Test Reporter MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables Claude Code to read and write issues on the Testing Platform via natural language, including listing projects, filtering issues, creating and updating issues, and adding comments.9-
- AlicenseAqualityAmaintenanceConnects AI coding assistants to Gaffer test history and coverage data to analyze project health, debug failures, and identify untested code areas. It enables tools to track test stability, cluster failures by root cause, and monitor code coverage trends across projects.339 npm1MIT
- AlicenseBqualityDmaintenanceIntegrates TestRail with Claude Code to enable AI-assisted test management workflows, including project, suite, test case, test run, and result operations.13828 npmMIT
- AlicenseAqualityAmaintenanceProvides coding agents with visibility into test health through tools for flaky test detection, test quality linting, and LLM evaluation harness, enabling them to triage failures, review test quality, and check prompt changes for regressions.9Apache 2.0
Tesults MCPofficial
AlicenseNot gradedqualityDmaintenanceConnect AI agents to your test results, insights, and targets. Query test runs, failures, flaky tests, and regressions across frameworks including Playwright, Jest, Pytest, Cypress and more.28 npmMIT
TDQS
A3.7/5.0
Scored across 9 tools
Disambiguation4/5
Most tools target distinct analytical questions (patterns, correlation, screenshots, consecutive failures). The main overlap is get_flaky_tests vs get_flaky_specs (test-level vs spec-level) and some tension between get_test_history and get_test_trend, but the descriptions explicitly clarify the differences. Boundaries are mostly clear.
Naming Consistency5/5
Every tool follows the consistent get_<entity> snake_case pattern (get_failure_patterns, get_test_history, get_flaky_tests, etc.). Naming is fully predictable with no stylistic deviations.
Tool Count5/5
Nine tools is well within a sensible range for a test analytics domain and each tool maps to a distinct analytical query. No bloat or redundancy that would suggest padding.
Completeness4/5
The surface covers failure patterns, flakiness, correlation, trends, screenshots, and consecutive failures well. Minor gaps exist—no tool to fetch individual run detail or list/search tests directly—but core triage and reliability-analysis workflows are covered.
Maintenance
ActivityInactive
ResponsivenessNo issues