Skip to main content
Glama

Related Servers

Alternatives to testrun-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      A
      quality
      D
      maintenance
      Wraps existing test frameworks (Jest, Vitest, Pytest) and exposes structured, LLM-optimized results via MCP tools with progressive disclosure and diff-aware execution.
      11
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to run, debug, and inspect Playwright end-to-end tests, returning structured pass/fail stats, failure diagnostics with actionable fix hints, live DOM inspection, selector validation, visual diffs, and flakiness verdicts instead of raw test output.
      11
      2,464 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models (Claude, ChatGPT, GitHub Copilot) to run and analyze local tests, rerun failures, and orchestrate QA workflows using existing UI and API test frameworks.
      3 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to run budgeted tests and checks under a countdown with a stop rule, shape long logs into concise failure summaries, and guard pre-existing test files against silent assertion rewrites. It also delivers relevance-filtered project memory and renders a token-and-time roadmap of the orchestrator and every subagent spawned for a task.
      7
      MIT

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    The tools mostly have distinct purposes: detection, listing, running, coverage, rerunning failures, flaky checks, and failure explanation. There is some overlap among run_tests, rerun_failed, flaky_check, and explain_failure because all execute tests, but the descriptions make their boundaries reasonably clear.

    Naming Consistency4/5

    Most names follow a verb_noun pattern (detect_runner, run_tests, rerun_failed, list_tests, explain_failure), and all use snake_case consistently. coverage_summary and flaky_check are noun-phrase deviations, but they remain readable and predictable.

    Tool Count5/5

    Seven tools is well-scoped for a test-runner MCP server. Each tool covers a distinct part of the test workflow without obvious redundancy.

    Completeness4/5

    The surface covers detection, listing, running, rerunning failures, coverage, flaky detection, and failure explanation, which is strong lifecycle coverage. Minor gaps include coverage being Python-only and no equivalent coverage or profiling support for JavaScript runners.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues