SkillFoxx

Lighthouse MCP

MCP server that runs Google Lighthouse on a page URL and returns page speed scores, metrics and audit categories

  • 219 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • The server starts Chrome and opens the given addresses, including localhost unless loopback access is turned off
  • Untrusted pages are best audited in an isolated environment
All reasons and checks

priyankark/lighthouse-mcpAuthor:priyankark

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/lighthouse-mcp

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The server starts Chrome and opens the given addresses, including localhost unless loopback access is turned off
  • Untrusted pages are best audited in an isolated environment

This is third-party code. Review the repository files before installing.

What it does

Lighthouse MCP wraps Google's Lighthouse tool. The agent passes a page URL, and the server starts Chrome, runs the audit and returns performance, accessibility, best-practices and SEO scores along with metrics. There are two tools: `run_audit` performs a full audit with a choice of categories, mobile or desktop emulation and network throttling, and `get_performance_score` returns only the performance score. A Claude Code request looks like this: what is the performance score for example.com. Audits run one at a time with a 120-second timeout, Chrome runs sandboxed, and addresses from private networks and cloud metadata are blocked.

Who it is for. Frontend developers and SEO specialists who want to measure page speed without leaving the agent session.

Good fit when

  • After a layout change the agent runs the page and compares the performance score before and after
  • Before a release the agent checks accessibility and SEO of the home page under mobile emulation
  • The agent compares desktop and mobile versions of one URL with and without network throttling
  • A local site on localhost is measured during development

Not a fit when

  • You need field data from real users: Lighthouse gives a lab measurement on one machine
  • The page is not reachable from the network where the server runs: Chrome has to open the address
  • You need continuous monitoring: the server runs a one-off audit and has no scheduler

Example request

Run Lighthouse for https://example.com under mobile emulation, show scores for all four categories and the three heaviest issues

MCP

Transport
stdio
Authentication
not required

Environment variables

AUDIT_ALLOW_LOOPBACK
The value false forbids auditing localhost and loopback addresses, used for public-only audits

Limitations

Running needs Node.js 22.19 or newer and a Chrome or Chromium browser. Audits run one at a time and stop after 120 seconds. By default localhost and loopback addresses are allowed, while private, link-local and cloud metadata addresses are blocked, including through redirects. For public-only audits set `AUDIT_ALLOW_LOOPBACK=false`. Untrusted pages are better opened in a separate environment with network isolation, because loopback access is allowed on purpose. The license is MIT.

How to disable. Remove the lighthouse block from the MCP client configuration. A global package is removed with `npm uninstall -g lighthouse-mcp`.

FAQ

How do I run Lighthouse MCP?

With `npx lighthouse-mcp` and no install, or after a global `npm install -g lighthouse-mcp`. Node.js 22.19 and Chrome are required.

What audit parameters exist?

`url` is required, `categories` picks performance, accessibility, best-practices and seo, `device` sets mobile or desktop and `throttling` turns on network throttling.

Can I audit a local site?

Yes, localhost and loopback addresses are allowed by default. `AUDIT_ALLOW_LOOPBACK=false` turns them off.

What is blocked for safety?

Private networks, link-local and cloud metadata addresses, including through redirects and page resources. Connections use validated IPs, which guards against DNS rebinding.

Is it in the MCP registry?

Yes, the server is published in the MCP registry as `io.github.priyankark/lighthouse-mcp`.

Discussion

No questions or reviews yet.

MCP servers
Official

An MCP server for evaluating LLM apps: an agent runs an example set, compares runs and shows the failing queries.

MCP serverExtended access62
Official

kogiQA MCP gives an agent a browser that finds page elements without selectors, for debugging web apps and writing e2e tests

MCP serverExtended access88
Needs a VPN

An MCP server that spins up several browser agents to test a site for broken links, UI bugs and accessibility issues

MCP serverExtended access836

MCP Accessibility Scanner runs axe checks, exercises keyboard focus and saves accessibility reports for web pages

MCP serverExtended access59

README in short

A short guide: features, four install options, client configuration, two tools with parameters and examples, requirements and a security section on blocking private addresses.

README badge

Report a problem