Lighthouse MCP server
io.github.priyankark/lighthouse-mcp·v0.1.9·210 starsMCP server for Google Lighthouse performance metrics
210 stars1.4k downloads/wk
Reviews
Write oneNobody has reviewed Lighthouse yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Lighthouse tools (2, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
get_performance_scoreGet just the performance score for a URL
run_auditwrite actionRun a Lighthouse audit on a URL
Public scan report
scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it
- Code scan3 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 18 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Lighthouse compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 93% of 48,243 servers
- Tools
- 2
- the typical server has 7
- Tools that change things
- 50%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 210
- more than 95% of 28,706 servers
- Downloads a week
- 1,400
- more than 95% of 12,306 servers with a package
What its tools let an agent do: 1 read · 1 run or deploy
Install Lighthouse in Claude Code, Cursor or VS Code
Runs npx -y lighthouse-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add lighthouse-mcp -- npx -y lighthouse-mcp
What the publisher says
From the Lighthouse repository's README, as published. We do not edit it. Read it on GitHub
Lighthouse MCP Server
An MCP server that wraps around Google's Lighthouse tool to help measure various performance metrics for web pages.
Features
- Run comprehensive Lighthouse audits on any URL
- Get performance scores and metrics
- Configure device emulation (mobile/desktop)
- Control network throttling
- Select specific audit categories
Installation
Option 1: From MCP Registry (Recommended)
This server is available in the Model Context Protocol Registry. Install it using your MCP client or Claude Desktop.
Option 2: Using npx
You can run the tool directly using npx without installation:
npx lighthouse-mcpOption 3: Global Installation
Install the package globally from npm:
npm install -g lighthouse-mcpThen run it:
lighthouse-mcpOption 4: Local Development
- Clone this repository
- Install dependencies:
npm install- Build the project:
npm run build- Run the server:
npm startMCP Configuration
When installed via npm (global or npx)
Add the following to your MCP settings configuration file:
{
"mcpServers": {
"lighthouse": {
"command": "npx",
"args": ["lighthouse-mcp"],
"disabled": false,
"autoApprove": []
}
}
}When using local development version
Add the following to your MCP settings configuration file:
{
"mcpServers": {
"lighthouse": {
"command": "node",
"args": ["/absolute/path/to/lighthouse-mcp/build/index.js"],
"disabled": false,
"autoApprove": []
}
}
}Replace /absolute/path/to/lighthouse-mcp with the actual path to this project.
Available Tools
run_audit
Run a comprehensive Lighthouse audit on a URL.
Parameters:
- url (required): The URL to audit
- categories (optional): Array of categories to audit (defaults to all)
- Options: "performance", "accessibility", "best-practices", "seo"
- device (optional): Device to emulate (defaults to "mobile")
- Options: "mobile", "desktop"
- throttling (optional): Whether to apply network throttling (defaults to true)
Example:
{
"url": "https://example.com",
"categories": ["performance", "accessibility"],
"device": "desktop",
"throttling": false
}getperformancescore
Get just the performance score for a URL.
Parameters:
- url (required): The URL to audit
- device (optional): Device to emulate (defaults to "mobile")
- Options: "mobile", "desktop"
Example:
{
"url": "https://example.com",
"device": "mobile"
}Example Usage
Once the MCP server is configured, you can use it with Claude:
What's the performance score for example.com?Claude will use the getperformancescore tool to analyze the website and return the results.
Requirements
- Node.js 22.19+
- Chrome/Chromium browser (for Lighthouse)
Endorsements
Security
Chrome runs with its sandbox enabled. Localhost, IPv4 loopback, and IPv6 loopback remain supported by default. Private, link-local, cloud metadata, and other non-public destinations are blocked, including requests made by redirects and page resources. Connections use validated IP addresses to prevent DNS rebinding. Because loopback access is intentional, audit only pages you trust to access services on your own machine. For hostile sites, use a separate environment with network isolation.
Audits are limited to one at a time and time out after 120 seconds. Chrome and the audit proxy are cleaned up after success or failure.
Public-only audits
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Lighthouse: common questions
- Is Lighthouse MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Lighthouse safety report
- How do I install Lighthouse?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Lighthouse need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Lighthouse maintained?
- The last commit was 53 days ago (2026-09-13). The latest release is v0.1.9.
- How does Lighthouse compare with other MCP servers?
- safety score 92/100 (higher than 93% of 48,243 servers); tools 2 (the typical server has 7); tools that change things 50% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.