Skip to main content
Glama
hmodali2611

Test Automation MCP Server

by hmodali2611
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Test Automation MCP Server

No user-submitted related servers found.

    Related Servers

    • TestPilot MCP

      Kirit2121
      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
    • Tesults MCP by tesults

      Tesults MCPofficial

      tesults
      A
      license
      Not graded
      quality
      C
      maintenance
      Connect 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.
      81 npm
      MIT

    • testrail-ai-mcp

      jagreehal
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to answer QA questions in a single call, covering run reports, failure grouping by root cause, flaky versus regressed test detection, and coverage gaps. Also exposes raw TestRail API access when a question needs it.
      MIT

    • qa-metrics-mcp

      Misfit1982
      A
      license
      A
      quality
      B
      maintenance
      Turns JUnit XML test reports from CI into queryable QA metrics, letting AI assistants answer plain-English questions about failures, flaky tests, regressions pinned to a commit, root-cause clusters, and performance drift. Also generates ready-to-share QA health reports and self-contained HTML dashboards without logging into separate tools.
      11
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct step in the test workflow: discovering suites, running tests, reading recent results, drilling into failures, querying fixtures, and filing a bug. The run_tests vs. get_test_results distinction is explicit: one executes, the other summarizes an existing report. get_failure_details is also clearly scoped to digging into named failing tests.

    Naming Consistency5/5

    All tools use consistent snake_case with a clear verb_noun pattern: list_test_suites, run_tests, get_test_results, get_failure_details, query_test_data, create_jira_bug. The convention is predictable throughout with no mixed styles.

    Tool Count5/5

    Six tools is well-scoped for a test automation server, covering the core workflow without redundant or filler operations. Each tool has a clear role in the run-inspect-debug-file lifecycle.

    Completeness4/5

    The surface covers the main workflow from listing suites through running tests, inspecting failures, querying fixtures, and filing a Jira bug. Minor gaps remain, such as historical results beyond the most recent report and suite configuration/management, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources