MCP server for Google Lighthouse performance metrics
io.github.priyankark/lighthouse-mcp — Model Context Protocol (MCP) Server
The io.github.priyankark/lighthouse-mcp server is an MCP server that wraps Google Lighthouse to measure web page performance metrics. It can run Lighthouse audits on any URL and return performance scores and related metrics, with options for device emulation, network throttling, and choosing specific audit categories.
🛠️ Key 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
🚀 Use Cases
Measuring web page performance using Lighthouse audit results
Running targeted audits by selecting audit categories
Comparing results across emulated mobile vs. desktop conditions
⚡ Developer Benefits
Works through the Model Context Protocol to retrieve Lighthouse outputs
Supports configurable execution via device emulation and network throttling
⚠️ Limitations
No additional functionality beyond wrapping Lighthouse is described in the provided data.
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
Set AUDIT_ALLOW_LOOPBACK=false to reject loopback destinations as well as private and metadata addresses. Hosted workers must use this setting and infrastructure egress isolation. Local development keeps loopback access by default.