Skip to main content
Glama
sharath9271-design

QA Copilot MCP Server

by sharath9271-design
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to QA Copilot MCP Server

No user-submitted related servers found.

    Related Servers

    • playwright-e2e-mcp

      trajectiq-ai
      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
      376 npm
      MIT

    • Autonomous QA Engineer MCP

      GolffyCoding
      F
      license
      Not graded
      quality
      B
      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.
      -

    • playwright-fixer-mcp

      BobChochola
      A
      license
      A
      quality
      D
      maintenance
      Automated 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
      MIT

    • playwright-e2e-mcp

      xsignon-secure
      A
      license
      A
      quality
      A
      maintenance
      Enables agents to run Playwright suites, diagnose failures from trace-level DOM, network and console evidence, and apply locator fixes that are re-run and reverted if still red. It also repeats failing tests for per-test flaky, regressed or broken verdicts and surfaces the same diagnosis and fix diffs in CI job summaries and PRs.
      12
      376 npm
      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

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct responsibility—summarizing test output, identifying flaky tests, explaining failures, generating test stubs, and fetching CI status. There is no meaningful overlap between any pair of tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with clear action-prefixed names: summarize_, list_, explain_, generate_, get_. Minor pluralization differences do not create confusion.

    Tool Count5/5

    Five tools cover a tightly scoped QA workflow—analyze results, detect flakiness, explain failures, generate tests, and check CI—without redundancy or bloat.

    Completeness4/5

    The core QA reporting and triage loop is well supported, from parsing reports to explaining failures and detecting flaky tests. Minor gaps like actionable test-edit or test-deletion operations are absent, but they fall outside the visible purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources