Playwright MCP Alternatives for Test Automation: CI Runs the File

The agent records a MCP walkthrough of login. Someone pastes the steps into the PR description. There is no tests/login.spec.ts. Nightly "automation" is a human rerunning the agent. That is not a suite.

Use the CLI only to draft. The merge gate is the file. Tag money paths @critical. Do not put @playwright/mcp in GitHub Actions required checks.

jobs:
  playwright:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 22
      - run: npm ci
      - run: npx playwright install --with-deps chromium
      - run: npx playwright test --grep @critical --reporter=github

import { test, expect } from "@playwright/test";

test("login @critical", async ({ page }) => {
  await page.goto("/login");
  await page.getByLabel("Email").fill("qa@example.com");
  await page.getByLabel("Password").fill(process.env.QA_PASSWORD!);
  await page.getByRole("button", { name: "Sign in" }).click();
  await expect(page.getByRole("heading", { name: "Overview" })).toBeVisible();
});

Decision context sits in the pillar on best Playwright MCP alternatives. Implementation at scale is AI quality engineering services or the Enterprise page. Not sure where your gaps are? Start with the free QA maturity assessment for a scored baseline.

• Pass: Deleting the Overview heading fails @critical on the PR. No MCP job is required.
• Fail: CI still invokes npx @playwright/mcp as the only check.
• Cleanup: Remove MCP from the workflow file. Keep install --with-deps chromium.