Skip to main content
Glama

Related Servers

Alternatives to testmcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to run a project's pytest, unittest, jest, or vitest suites and get back compact structured results with trimmed tracebacks, collection errors kept apart from real failures, and the slowest tests. Agents can then re-run just the failures, expand one failure with local variables, repeatedly execute a single test to judge flakiness, and inspect Python coverage gaps, all under a hard timeout that kills the whole process tree.
      7
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP tools that give LLM agents a full QA engineer workflow: scanning projects, generating deterministic test suites, executing them across browser/API/mobile, diagnosing failures, and proposing fixes that require human approval.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely run test suites over MCP, returning concise JUnit-based results, trimmed tracebacks, rerun-failed support, and flaky-test detection while handling timeouts, process cleanup, and bounded output.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible editors to orchestrate test runs, debug failures, analyze visual regressions, run accessibility audits, and manage test cases through natural language.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI coding agents to obtain clean failing-test context, ranked suspect lines, runtime value comparisons, bounded code search, and patch verification so they can fix Python test failures with fewer tokens.
      MIT

    TDQS

    A3.5/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have distinct resource+action targets: run_tests vs run_affected, list_runs vs list_artifacts, and get_failures vs get_test_detail are separable. However, get_failures and get_test_detail both surface failure detail, and parse_log and parse_artifact both 'parse' test data, creating mild potential for misselection.

    Naming Consistency4/5

    Nearly all names follow a consistent snake_case verb_noun pattern (list_runs, run_tests, get_failures, parse_artifact, rerun_failed). The lone outlier is 'discover', a bare verb with no noun object, which is a minor deviation from the otherwise uniform convention.

    Tool Count5/5

    11 tools is well-scoped for a test-runner server, with each tool covering a distinct facet (discovery, execution, failure drill-down, coverage, artifact parsing). No redundant or filler tools appear.

    Completeness4/5

    The surface covers the full test lifecycle: discovery, running (full and affected), failure inspection, reruns, coverage, and CI log/artifact parsing. Minor gaps exist (e.g., no config/watch or artifact listing beyond GitHub Actions), but core workflows are complete.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data