Skip to content
Back to search

lighthouse-mcp

Allows AI assistants such as Amp/Cline/Cursor/Claude Code/Codex/GitHub Copilot to use Google's lighthouse tool to measure perf metrics for your webpage. You can then run an agentic loop and get the assistants to optimize those metrics!

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/priyankark/lighthouse-mcp with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/priyankark/lighthouse-mcp'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/priyankark--lighthouse-mcp/badge.svg)](/listings/priyankark--lighthouse-mcp)

HTML

<a href="/listings/priyankark--lighthouse-mcp"><img src="/api/listings/priyankark--lighthouse-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Option 1: From MCP Registry (Recommended)

This server is available in the [Model Context Protocol Registry](https://registry.modelcontextprotocol.io/servers/io.github.priyankark/lighthouse-mcp). 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-mcp

Option 3: Global Installation

Install the package globally from npm:

npm install -g lighthouse-mcp

Then run it:

lighthouse-mcp

Option 4: Local Development

1. Clone this repository 2. Install dependencies:

   npm install

3. Build the project:

   npm run build

4. Run the server:

   npm start

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 172 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Lighthouse MCP Server
  2. An MCP server that wraps around Google's Lighthouse tool to help measure various performance metrics for web pages.
  3. ## Features
  4. - Run comprehensive Lighthouse audits on any URL
  5. - Get performance scores and metrics
  6. - Configure device emulation (mobile/desktop)
  7. - Control network throttling
  8. - Select specific audit categories
  9. ## Installation
  10. ### Option 1: From MCP Registry (Recommended)
  11. This server is available in the [Model Context Protocol Registry](https://registry.modelcontextprotocol.io/servers/io.github.priyankark/lighthouse-mcp). Install it using your MCP client or Claude Desktop.
  12. ### Option 2: Using npx
  13. You can run the tool directly using npx without installation:
  14. ```bash
  15. npx lighthouse-mcp
  16. ```
  17. ### Option 3: Global Installation
  18. Install the package globally from npm:
  19. ```bash
  20. npm install -g lighthouse-mcp
  21. ```
  22. Then run it:
  23. ```bash
  24. lighthouse-mcp
  25. ```
  26. ### Option 4: Local Development
  27. 1. Clone this repository
  28. 2. Install dependencies:
  29. ```bash
  30. npm install
  31. ```
  32. 3. Build the project:
  33. ```bash
  34. npm run build
  35. ```
  36. 4. Run the server:
  37. ```bash
  38. npm start
  39. ```
  40. ## MCP Configuration
  41. ### When installed via npm (global or npx)
  42. Add the following to your MCP settings configuration file:
  43. ```json
  44. {
  45. "mcpServers": {
  46. "lighthouse": {
  47. "command": "npx",
  48. "args": ["lighthouse-mcp"],
  49. "disabled": false,
  50. "autoApprove": []
  51. }
  52. }
  53. }
  54. ```
  55. ### When using local development version
  56. Add the following to your MCP settings configuration file:
  57. ```json
  58. {
  59. "mcpServers": {
  60. "lighthouse": {
  61. "command": "node",
  62. "args": ["/absolute/path/to/lighthouse-mcp/build/index.js"],
  63. "disabled": false,
  64. "autoApprove": []
  65. }
  66. }
  67. }
  68. ```
  69. Replace `/absolute/path/to/lighthouse-mcp` with the actual path to this project.
  70. ## Available Tools
  71. ### run_audit
  72. Run a comprehensive Lighthouse audit on a URL.
  73. **Parameters:**
  74. - `url` (required): The URL to audit
  75. - `categories` (optional): Array of categories to audit (defaults to all)
  76. - Options: "performance", "accessibility", "best-practices", "seo"
  77. - `device` (optional): Device to emulate (defaults to "mobile")
  78. - Options: "mobile", "desktop"
  79. - `throttling` (optional): Whether to apply network throttling (defaults to true)
  80. **Example:**
  81. ```json
  82. {
  83. "url": "https://example.com",
  84. "categories": ["performance", "accessibility"],
  85. "device": "desktop",
  86. "throttling": false
  87. }
  88. ```
  89. ### get_performance_score
  90. Get just the performance score for a URL.
  91. **Parameters:**
  92. - `url` (required): The URL to audit
  93. - `device` (optional): Device to emulate (defaults to "mobile")
  94. - Options: "mobile", "desktop"
  95. **Example:**
  96. ```json
  97. {
  98. "url": "https://example.com",
  99. "device": "mobile"
  100. }
  101. ```
  102. ## Example Usage
  103. Once the MCP server is configured, you can use it with Claude:
  104. ```
  105. What's the performance score for example.com?
  106. ```
  107. Claude will use the `get_performance_score` tool to analyze the website and return the results.
  108. ## Requirements
  109. - Node.js 22.19+
  110. - Chrome/Chromium browser (for Lighthouse)
  111. ## Security
  112. 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.
  113. 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.
  114. ### Public-only audits
  115. 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.
  116. ## Maintainer CI and releases
  117. GitHub Actions runs the build, network and release-policy tests, npm security audit, and real Chrome smoke tests on the minimum supported Node version and Node 24. Node 24 also installs the npm tarball in a clean temporary project and checks its executable, dependencies, MCP version, and browser audits.
  118. Every push to `main` runs the release pipeline. When package files change, it automatically increments the patch version (or honors a larger version already committed), synchronizes package metadata, repeats validation, commits and tags the release, publishes to npm with provenance, and creates a GitHub release. Changes limited to documentation, tests, or workflows do not publish a new version. Runtime server versions come from `package.json`.
  119. Dependabot checks npm and GitHub Actions weekly. A successful PR CI run automatically merges npm updates only when all existing changed dependencies are stable patch/minor upgrades and only `package.json` / `package-lock.json` changed. Major upgrades, 0.x minor upgrades, downgrades, prereleases, and GitHub Actions changes require review. The merge job runs only trusted code from `main`, verifies the tested PR head, and explicitly dispatches publishing after a bot merge.
  120. npm publishing uses the `npm` GitHub environment and an npm trusted publisher for `priyankark/lighthouse-mcp`, workflow `publish.yml`, environment `npm`, with direct publishing allowed. No npm token is stored in GitHub. The environment accepts deployments only from `main`.
  121. To retry a failed release, rerun the **Publish** workflow or run `./release.sh`. The pipeline reuses an unpublished version and skips an already published, unchanged package. If a reserved release tag points to different code, it stops rather than overwriting that version. For a breaking change, update `package.json` and `package-lock.json` to the intended major/minor version in the reviewed PR before merging.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.