A
licenseB
qualityD
maintenanceAutonomous QA testing MCP server that analyzes, fixes, and learns from test failures. Integrates with IDE and Slack to provide cause and fix in plain language.
31
12 npm
MIT
test-genie-mcp
Related Servers
Alternatives to test-genie-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAutomated Playwright E2E test repair powered by a self-improving, governed MCP server that runs failing tests, collects failure artifacts, reasons about root causes, validates and applies fixes, and re-runs to verify.12-
- AlicenseNot gradedqualityBmaintenanceMCP server for self-healing Selenide + Cucumber regression tests, using AI to fix failed locators and rerun tests.MIT
AWARSEofficial
AlicenseAqualityBmaintenanceSelf-healing browser automation MCP server integrating Playwright with LLM-assisted locator repair.61MIT- FlicenseBqualityBmaintenanceMCP server for AI-powered QA analysis. It enables analyzing test failures, identifying root causes, suggesting fixes, classifying defects, detecting flaky tests, and generating test cases and bug reports.10-
- AlicenseNot gradedqualityDmaintenanceAI-powered E2E testing MCP server. Point at a URL — AI generates test scenarios, runs Playwright tests, and self-heals failures automatically. Works on Canvas and Flutter Web apps.7MIT
TDQS
B3/5.0
Scored across 23 tools
Disambiguation4/5
Most tools have distinct purposes (e.g., analyze_app_structure vs analyze_code_deep vs analyze_performance). The main overlap is between the comprehensive diagnose_project and the individual detectors, but their descriptions clearly differentiate them. Slight potential confusion exists between analyze_code_deep and detect_logic_errors due to overlapping 'issues' coverage.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (e.g., analyze_app_structure, run_scenario_test, generate_report). The naming convention is uniform across the entire set, with no mixed styles or vague verbs.
Tool Count3/5
23 tools is on the heavier side and falls into the borderline range for a typical MCP server. While the domain is broad and each tool has a role, the redundancy between combined and stand-alone detectors (e.g., diagnose_project vs detect_race_conditions) adds some unnecessary weight.
Completeness4/5
The tool set covers a full lifecycle: analysis, scenario generation, planning, execution, detection, fixing, reporting, and CI/CD. However, there are minor gaps such as no explicit tools for listing or deleting stored scenarios/test plans, which may require workarounds.
Maintenance
ActivityStale
ResponsivenessNo issues