Skip to main content
Glama
xsignon-secure

playwright-e2e-mcp

by xsignon-secure
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to playwright-e2e-mcp

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
      55 npm
      MIT

    • tuxedo-qa

      jonathan-ponciano
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to create, run, autocorrect, and monitor Playwright tests for your app with a local dashboard, credential vault, and public status page.
      16
      MIT
    • QualityMax QA MCP by Quality-Max

      QualityMax QA MCPofficial

      Quality-Max
      A
      license
      A
      quality
      A
      maintenance
      Enables coding agents to independently verify web changes by scanning pages, inspecting UI structure, generating Playwright reproductions, and executing tests with structured QA evidence.
      4
      222 npm
      4
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A4.1/5.0

    Scored across 11 tools

    Disambiguation4/5

    The tools form a clear pipeline (run-test → get-failure → suggest-fix) with distinct analysis tools (analyze-history for history, diagnose-flaky for re-running), so most purposes are separable. However, inspect-page vs validate-selector overlap (both surface live-page locators), and analyze-history's 'flaky' view vs diagnose-flaky could be confused by an agent unsure which layer to use.

    Naming Consistency5/5

    Every name follows a verb_noun kebab-case pattern (run-test, get-failure, suggest-fix, list-tests, validate-selector, generate-e2e-test, compare-visual-state, diagnose-flaky, analyze-history, inspect-page, get-run-status). The only minor deviation is the compound verb in get-run-status, which is still readable and consistent.

    Tool Count5/5

    11 tools is well within the sweet spot and each maps to a real step in the e2e workflow (run, inspect, diagnose, fix, scaffold, visual-check). Nothing feels padded or redundant at the count level.

    Completeness4/5

    The surface covers the full diagnose-and-fix lifecycle plus test generation, listing, selector validation and visual regression. Minor gaps exist: no explicit tool to manage/reset visual baselines or clean run artifacts, though agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources