允许 AI 助手(如 Amp/Cline/Cursor/Claude Code/Codex/GitHub Copilot)使用 Google 的 lighthouse 工具来测量网页的性能指标。您可以
允许 AI 助手(如 Amp/Cline/Cursor/Claude Code/Codex/GitHub Copilot)使用 Google 的 lighthouse 工具来测量网页的性能指标。您可以
An MCP server that wraps around Google's Lighthouse tool to help measure various performance metrics for web pages.
This server is available in the Model Context Protocol Registry. Install it using your MCP client or Claude Desktop.
You can run the tool directly using npx without installation:
npx lighthouse-mcpInstall the package globally from npm:
npm install -g lighthouse-mcpThen run it:
lighthouse-mcpnpm installnpm run buildnpm startAdd the following to your MCP settings configuration file:
{
"mcpServers": {
"lighthouse": {
"command": "npx",
"args": ["lighthouse-mcp"],
"disabled": false,
"autoApprove": []
}
}
}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.
Run a comprehensive Lighthouse audit on a URL.
Parameters:
url (required): The URL to auditcategories (optional): Array of categories to audit (defaults to all)device (optional): Device to emulate (defaults to "mobile")throttling (optional): Whether to apply network throttling (defaults to true)Example:
{
"url": "https://example.com",
"categories": ["performance", "accessibility"],
"device": "desktop",
"throttling": false
}Get just the performance score for a URL.
Parameters:
url (required): The URL to auditdevice (optional): Device to emulate (defaults to "mobile")Example:
{
"url": "https://example.com",
"device": "mobile"
}Once the MCP server is configured, you can use it with Claude:
What's the performance score for example.com?Claude will use the get_performance_score tool to analyze the website and return the results.
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.
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.
暂无开放 Issues,或尚未同步最近议题。