Hosted MCP server/Development

Playwright E2E MCP server

Provider setup path

Playwright E2E runs, debugs, and inspects Playwright end-to-end tests from an AI agent, returning structured results with file:line failure diagnostics, live DOM inspection, selector validation, visual diffs, and flaky-test diagnosis. The maintainer documents a local npm install, npx -y playwright-e2e-mcp init. The hosted URL answers with 401 and an OAuth protected-resource challenge for scope mcp, so it is not an anonymous endpoint and the local stdio path is canonical.

OAuth (bearer token, scope mcp) Server not checked yet Reviewed 2026-11-16
About

Where it fits

QA engineers and developers debugging Playwright failures with selectors, DOM inspection, and visual diffs.

  • Initialise the local npm server.
  • Run Playwright tests from an agent.
  • Authorize the hosted endpoint with OAuth scope mcp.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local npm server

The maintainer documents a local npm install. The hosted URL answers with 401 and an OAuth protected-resource challenge (scope mcp); it is not an anonymous endpoint. The local stdio path is canonical.

  1. Initialise the local server

    Run the provider's npm initialiser for local Playwright E2E use.

    npx -y playwright-e2e-mcp init
  2. Register the local server

    Add the generated command to your MCP client.

  3. Or authorize the hosted endpoint

    If you use the hosted URL, complete OAuth with scope mcp; a tokenless request returns 401.

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Playwright E2E repositoryhttps://github.com/trajectiq-ai/E2E