Playwright MCP Server

Playwright Lighthouse Audit

Local serverstdioGo

What is the Playwright MCP server?

Most browser automation work still happens through a UI a human drives. Playwright MCP server moves it into the conversation instead. Playwright Lighthouse Audit.

The short version

Lighthouse is a tool developed by Google that analyzes web apps and web pages, collecting modern performance metrics and insights on developer best practices.

The tools it exposes

The server publishes 3 tools. What each one is for:

  • v3.x.x — 10
  • v4.x.x — 11
  • Installation — Add the playwright-lighthouse, playwright & lighthouse libraries to your project:

Getting it running

The server ships on npm as playwright-lighthouse, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What it needs from you

Configuration is passed through the environment: LIGHTHOUSE_LAMBDATEST, LT_ACCESS_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Playwright's toolset — v3.x.x, v4.x.x, Installation — is a fair guide to whether it matches your workflow. It is maintained by abhinaba-ghosh; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
v3.x.x10
v4.x.x11
InstallationAdd the playwright-lighthouse, playwright & lighthouse libraries to your project:

How to install the Playwright MCP server

{
  "mcpServers": {
    "playwright-lighthouse": {
      "command": "npx",
      "args": ["-y", "playwright-lighthouse"],
      "env": {
        "LIGHTHOUSE_LAMBDATEST": "your-value",
        "LT_ACCESS_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
LIGHTHOUSE_LAMBDATESTConfiguration value read at startup.Optional
LT_ACCESS_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Playwright to v3.x.x.
  • Use Playwright to v4.x.x.
  • Use Playwright to Installation.

Frequently asked questions

It connects Playwright to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (v3.x.x, v4.x.x, Installation) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Playwright directly.