# lighthouse-mcp [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/priyankark/lighthouse-mcp  
**GitHub Stars:** 212  
**npm Downloads (last month):** 5602  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/lighthouse-mcp

## Description
MCP server for Google Lighthouse performance metrics

## Tools
Capabilities this server exposes over MCP:

- **run_audit** — Run a Lighthouse audit on a URL
- **get_performance_score** — Get just the performance score for a URL

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "lighthouse-mcp": {
    "command": "npx",
    "args": ["lighthouse-mcp"]
  }
}
```

## Documentation

## What lighthouse-mcp does

The lighthouse-mcp MCP server connects an MCP client to Google Lighthouse, allowing an agent to request web audits for a supplied URL. It returns Lighthouse results for selected audit areas or a performance score, depending on the tool used.

A complete audit can cover performance, accessibility, best practices, and SEO. The request can select one or more of these categories, choose mobile or desktop emulation, and enable or disable network throttling. Category selection defaults to all supported categories, while device emulation defaults to mobile and throttling defaults to enabled.

The server is intended for checking publicly reachable web pages and trusted local pages. It is useful for conversational checks such as asking an agent to assess a site's performance or compare an audit configured for desktop rather than mobile.

## How it works

The lighthouse-mcp MCP server runs as a Node.js process and uses a Chrome or Chromium browser to perform Lighthouse audits. MCP clients send tool requests containing the target URL and optional audit settings. Audits are limited to one at a time and have a 120-second timeout. Chrome and the audit proxy are cleaned up after an audit succeeds or fails.

Two tools are available:

- `run_audit` performs a comprehensive audit. It requires `url` and accepts `categories`, `device`, and `throttling`.
- `get_performance_score` returns only the performance score. It requires `url` and optionally accepts `device`.

Chrome keeps its sandbox enabled. By default, loopback destinations are supported, while private, link-local, cloud metadata, and other non-public destinations are blocked. Redirects and page resources are subject to the same restrictions, and connections use validated IP addresses to help prevent DNS rebinding.

## Setup and configuration

The documented runtime requirement is Node.js 22.19 or newer plus Chrome or Chromium. The package can be started directly with `npx lighthouse-mcp`, installed globally with `npm install -g lighthouse-mcp`, or built from a cloned repository with `npm install`, `npm run build`, and `npm start`.

For an npm or npx installation, configure the MCP client to run `npx` with `lighthouse-mcp` as its argument. A local build can be launched with `node` and the absolute path to `build/index.js`.

Set `AUDIT_ALLOW_LOOPBACK=false` when loopback access must also be rejected. The documentation recommends this setting for hosted workers, together with infrastructure egress isolation. Local development allows loopback access by default, so only audit pages that are trusted to access services on the machine.

## Limitations and notes

The server does not document persistent storage, scheduled audits, result history, or comparison features. Each request performs an audit through the local browser environment. Sites that require access to blocked private or metadata destinations may not be suitable targets. Hostile sites should be audited in a separate environment with network isolation.

The server is available through the MCP Registry, and the README specifically mentions installation through an MCP client or Claude Desktop.

_Full upstream README: https://allmcps.com/mcp/lighthouse-mcp/readme_