Playwright E2E MCP vs TesterArmy

A side-by-side look at the Playwright E2E MCP and TesterArmy MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Playwright E2E MCP logoPlaywright E2E MCPBrowser Automation · Local subprocess (stdio)Diagnose and fix failing Playwright tests: trace analysis, verified locator fixes, flaky ranking.61GoodAuth: not declaredTesterArmy logoTesterArmyBrowser Automation · Local subprocess (stdio)Agents that test your web and mobile app like real users, on every pull request.47FairAuth: not declared

Verdict: choose Playwright E2E MCP for browser automation work as a local process; choose TesterArmy for browser automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Playwright E2E MCP logoChoose Playwright E2E MCP when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: PW_MCP_STORAGE_STATE.
  • You want tools like run-test, get-run-status, get-failure.
Explore Playwright E2E MCP

TesterArmy logoChoose TesterArmy when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
Explore TesterArmy

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPlaywright E2E MCP logoPlaywright E2E MCPTesterArmy logoTesterArmy
CategoryBrowser AutomationBrowser Automation
Quality signal61/100 · Good47/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingFreeNot declared
Required env varsPW_MCP_STORAGE_STATENone listed
Verified ownerCommunity listingCommunity listing
GitHub stars070
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools12Not listed

Tools & capabilities

Playwright E2E MCP tools 12

  • run-testRun the project's Playwright tests: stats plus each failure's file:line, kind and message. Diagnoses missing installs, dead dev servers, syntax errors, crashes and timeouts (kills the tree, keeps partial results). Reports progress; background: true returns a run id for long suites. Runs are recorded for analyze-history.
  • get-run-statusProgress (tests done/total, failures so far) or the final result of a run-test background run; the result becomes the last run for get-failure. waitSeconds waits; cancel stops it. Default: the latest run.
  • get-failureAnalyze one failure from the most recent run-test execution: full message and code frame, expected vs actual, stack trace, failed network requests (4xx/5xx and dead endpoints), console errors, failure kind (assertion/timeout/browser-crash/syntax/config/server-unreachable) and concrete next steps. Use run-test first.
  • suggest-fixPatch a failure from the last run: a drifted locator is matched against the DOM at failure (trace, or live url) and replaced with one proven unique; changed copy gets the new expected text. Returns a diff and confidence; apply: true writes it, re-runs the test and reverts if still red. Refuses when the element is truly missing (app bug).
  • inspect-pageOpen a URL headlessly and return its elements with Playwright locators proven unique on the page (role + name first), CSS selectors, visibility, text and console messages. storageState/headers open it signed in; actions click/fill first to reach a state. view 'locators' is the compact map.
  • list-testsList the Playwright tests available in the project (file, line, full title, projects), with optional filtering. Uses `playwright test --list` when Playwright works and falls back to a source scan when the install or config is broken, reporting why.
  • validate-selectorCheck a CSS selector, Playwright selector or locator (getByRole/getByTestId…, .first(), .filter()) on a live page: validity, match count (actions need exactly 1), sample matches and a sturdier verified locator for each. Accepts storageState/headers/actions.
  • audit-accessibilityRun axe-core on a live page (WCAG 2.2 AA by default) and return violations worst first, each with the offending elements as verified Playwright locators, the fix, and a regression check to paste into a spec. Accepts storageState/headers/actions to audit pages behind a login or after a step.
  • generate-e2e-testScaffold a Playwright test from a description using the project's REAL selectors. Scans the agent's recent file changes (git working tree / last commit, mtime fallback), extracts data-testid / role / label / placeholder / id locators with their source locations, optionally cross-checks them against the live page, writes a ready-to-run spec, and returns next steps.
  • compare-visual-stateVisual regression check: screenshot a live page (or element), compare it to a stored baseline, and report how many pixels changed, WHERE they changed (bounding regions), and the average color shift ("blue → red"). First call saves the baseline; later calls compare. Writes a red-highlighted diff image for review.
  • diagnose-flakyRepeat failing tests with retries disabled and return a per-test, evidence-based verdict: CONSISTENTLY FAILING (real bug), FLAKY (pass/fail counts, error-signature variance, duration spread) or NOT REPRODUCING. Runs all repetitions in one process by default. `isolate: true` also re-runs the failures with one worker to tell parallelism bugs (shared state) from flakiness inside the test; `order: true` (Playwright 1.64+) runs the files in random orders to catch tests that depend on what ran before them. Defaults to the tests that failed in the most recent run.
  • analyze-historyAnalyze the local run history (.playwright-e2e-mcp/history.jsonl, written by every run): 'flaky' ranks tests that flip pass/fail and lists broken or regressed ones; 'patterns' groups failures by cause; 'test' shows one test's timeline.

TesterArmy tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Playwright E2E MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "playwright-e2e-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-e2e-mcp"
      ],
      "env": {
        "PW_MCP_STORAGE_STATE": "YOUR_PW_MCP_STORAGE_STATE_HERE"
      }
    }
  }
}

TesterArmy

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "testerarmy": {
      "command": "npx",
      "args": [
        "-y",
        "testerarmy"
      ]
    }
  }
}

Frequently asked questions

Playwright E2E MCP is categorized under Browser Automation and uses a local stdio subprocess. TesterArmy belongs to Browser Automation and uses a local stdio subprocess. Pick Playwright E2E MCP for browser automation work and TesterArmy for browser automation.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Playwright E2E MCP is listed as free. TesterArmy has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add playwright-e2e-mcp and testerarmy as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Playwright E2E MCP has a quality signal of 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars. TesterArmy has 47/100 (Fair) with 1 views, 0 installs and 70 GitHub stars.