A
licenseA
qualityD
maintenanceEnables AI agents to run reusable Playwright test fixtures against live deployments, providing structured test results, screenshots, and assertions.
3
MIT
playwright-e2e-mcp
by trajectiq-ai
Related Servers
Alternatives to playwright-e2e-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI coding assistants to generate, score, run, and auto-heal Playwright E2E tests while enforcing domain-driven page object architecture and anti-flakiness rules.8MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to inspect, debug, and test web pages using Playwright. Provides comprehensive DOM inspection, visibility debugging, layout validation, and element finding capabilities in real browser environments.3466 npm5MIT
- AlicenseAqualityAmaintenanceEnables 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.12376 npmMIT
- AlicenseAqualityDmaintenanceRun real Playwright E2E tests from your AI coding agent.43 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables automated end-to-end testing powered by Playwright where test cases are defined in natural language and executed by AI. Uses lightweight snapshot analysis with vision mode fallback for sophisticated testing scenarios.3Apache 2.0
TDQS
A4/5.0
Scored across 11 tools
Disambiguation4/5
Tools map to distinct stages of the Playwright workflow: listing, running, monitoring, failure analysis, fixing, generation, visual comparison, selector validation, flaky diagnosis, and history. Overlap exists between diagnose-flaky and analyze-history, and between get-failure and get-run-status, but descriptions clarify the boundaries.
Naming Consistency5/5
All tool names use kebab-case with a consistent verb-first pattern (run-test, get-failure, list-tests, validate-selector, etc.). Minor variation in noun length does not break the convention.
Tool Count5/5
11 tools is well within the ideal 3–15 range. Each tool addresses a distinct aspect of Playwright E2E testing without obvious redundancy.
Completeness4/5
The core lifecycle is well covered: list tests, run tests, monitor runs, analyze failures, suggest fixes, generate tests, validate selectors, compare visual state, diagnose flakiness, and analyze history. Minor gaps include running a specific test or reading a single test's code, but agents can work around these.
Maintenance
ActivityMaintained
ResponsivenessNo issues