mcp-test-runner
Related Servers
Alternatives to mcp-test-runner
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Node.js server that integrates with pytest to facilitate the ModelContextProtocol (MCP) service tools, enabling test execution recording and environment tracking.6-
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables automated maintenance and code analysis for Python/pytest repositories in isolated Docker environments. It supports read-only investigations, fix-and-verify tasks, and provides full audit trails with SQLite event history and artifact exports.MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for safety-first automation and app QA, exposing deterministic tools to control graphical apps, browsers, terminals, Android devices, VMs, and SSH hosts.2 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceA universal AI-powered testing server built on the Model Context Protocol (MCP). Allows AI agents to inspect, execute, test, monitor, debug, and report on software projects.3GNU Lesser General Public v2.1 only
- AlicenseNot gradedqualityCmaintenanceMCP server for test impact analysis and code intelligence. Maps tests to code and git history to determine impacted tests, risk scores, and ownership for AI coding agents.3MIT
- -licenseNot gradedqualityNot gradedmaintenanceEnables automated testing and coverage reporting for MCP services with test execution, file generation, and mock service creation. Provides comprehensive testing infrastructure including Jest integration, coverage reports, and health checks for the MCP ecosystem.-
TDQS
Scored across 6 tools
The tool names clearly differentiate between different testing frameworks (pytest vs jest), single test execution, output parsing, coverage, and health. Without descriptions, there is slight potential confusion between run_pytest and run_single_test, but names are sufficiently distinct.
Three tools use the 'run_' prefix (run_pytest, run_jest, run_single_test), but parse_test_output, get_coverage_summary, and health deviate. The pattern is mixed but still readable and not chaotic.
With 6 tools, the server covers essential test runner operations: running tests by framework, running a single test, parsing output, coverage, and health check. Each tool serves a distinct purpose without unnecessary bloat.
The tool set covers core testing workflows: running tests (multiple frameworks), analyzing results (parse output, coverage), and health monitoring. Minor gaps like a combined test runner or report generation exist but do not hinder basic usage.