Log inSubmit server
Lighthouse MCP logo

Lighthouse MCP

Run Google Lighthouse audits through MCP with configurable URLs, categories, device emulation, and network throttling.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Lighthouse MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "lighthouse-mcp": {
      "command": "npx",
      "args": [
        "lighthouse-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 2 tools correctly (Today).

Overview

Google Lighthouse audits are exposed through the lighthouse-mcp MCP server for agent-driven web performance checks. It provides tools for complete audits and performance-only scores, with options for audit categories, mobile or desktop emulation, and network throttling. Run it through npx, a global npm install, or a locally built Node.js project, then register it as an MCP server in your client. Reach for it when an agent needs repeatable Lighthouse measurements for a trusted URL.

Use cases

  • Audit a website's performance and accessibility
  • Check a page's Lighthouse performance score
  • Compare mobile and desktop audit results
  • Run SEO and best-practices checks for a URL

Key features

  • Run comprehensive Lighthouse audits
  • Return performance-only scores
  • Select performance, accessibility, best-practices, or SEO categories
  • Emulate mobile or desktop devices
  • Enable or disable network throttling
  • Restrict loopback and private network access

Tools2

What Lighthouse MCP lets your agent do. Expand a tool for its parameters.

Verified live~201 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/5 checks healthy over the last 40d

What it can do

From the 2 tools this server returned when we ran it.

Makes network requests · 2Read-only tools · 2
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age564 days
Maintainers1

Observed 2026-10-24 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · lighthouse-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars212Stargazers on the source repository.
npm downloads5.6kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed2Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Lighthouse MCP works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Lighthouse MCP

lighthouse-mcp is an MCP server that connects AI clients to Google Lighthouse through a local Node.js process and Chrome or Chromium. Its main tools are run_audit for category-based audits and get_performance_score for performance-only checks, with mobile or desktop emulation and optional network throttling.

Install it with npx, npm globally, or from source. Run `npx lighthouse-mcp` directly, use `npm install -g lighthouse-mcp` followed by `lighthouse-mcp`, or clone the repository, install dependencies, build it, and start the local server.

It requires Node.js 22.19 or newer and Chrome or Chromium. An MCP client must also be configured to launch the server, either with `npx lighthouse-mcp` or with Node.js pointing to a locally built `build/index.js` file.

Yes, localhost and IPv4 or IPv6 loopback destinations are supported by default. Set `AUDIT_ALLOW_LOOPBACK=false` to reject loopback as well as private and metadata addresses, and use network isolation for hosted workers or untrusted sites.

The client configuration can also point to a locally built Node.js entry point.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLighthouse MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/lighthouse-mcp?style=directory)](https://allmcps.com/mcp/lighthouse-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/lighthouse-mcp"><img src="https://allmcps.com/api/badge/lighthouse-mcp?style=directory" alt="Lighthouse MCP on AllMCPs" /></a>