Lighthouse MCP Server

A Model Context Protocol (MCP) server that provides comprehensive web performance auditing and analysis capabilities using Google Lighthouse. This server enables LLMs and AI agents to perform detailed website performance assessments, accessibility audits, SEO analysis, security checks, and Core Web Vitals monitoring.

<a href="https://glama.ai/mcp/servers/@danielsogl/lighthouse-mcp-server">

</a>

🌟 Key Features

- 🚀 Performance Analysis: Complete Lighthouse audits with Core Web Vitals, performance scores, and optimization recommendations
- ♿ Accessibility Audits: WCAG compliance checking and accessibility score analysis
- 🔍 SEO Analysis: Search engine optimization audits and best practice recommendations
- 🔒 Security Assessment: HTTPS, CSP, and security vulnerability scanning
- 📊 Resource Analysis: JavaScript, CSS, image, and font optimization opportunities
- 📱 Mobile vs Desktop: Comparative analysis across devices with throttling options
- ⚡ Core Web Vitals: LCP, FID, CLS monitoring with threshold checking
- 🎯 Performance Budgets: Custom performance thresholds and budget monitoring
- 📚 Reference Resources: Built-in guidelines and best practices for web performance, accessibility, SEO, and security

🛠️ Requirements

- Node.js 22.0.0 or newer
- Chrome/Chromium browser (automatically managed by Lighthouse)
- VS Code, Cursor, Windsurf, Claude Desktop, or any other MCP client

🚀 Getting Started

Install the Lighthouse MCP server with your preferred client using one of the configurations below:

{
  "mcpServers": {
    "lighthouse": {
      "command": "npx",
      "args": ["@danielsogl/lighthouse-mcp@latest"]
    }
  }
}

Persistent Chrome Profiles (Login Sessions)

If you need authenticated sessions, launch with a persistent Chrome profile and run headed:

{
  "mcpServers": {
    "lighthouse": {
      "command": "npx",
      "args": [
        "@danielsogl/lighthouse-mcp@latest",
        "--profile-path",
        "<profile-path>",
        "--no-headless"
      ]
    }
  }
}

You can pass extra Chrome flags with --chrome-flag, for example --chrome-flag=--disable-gpu.
If the flag value starts with -- and matches a known option name, prefer --chrome-flag=... to avoid parsing it as a top-level option.
Profile mode disables Lighthouse's storage reset so cookies and local storage persist between runs.
If --user-data-dir points to a missing directory, it will be created and treated as a fresh profile.
Set --profile-path to the Profile Path shown in chrome://version (e.g. .../Default).
Note: Chrome's remote debugging requires a non-default user data directory, so reuse a dedicated profile directory instead of the system default.
You can also pass --user-data-dir + --profile-directory separately if you prefer.
Attaching with --chrome-port alone does not preserve storage; include a profile flag to keep sessions.

CLI Options

Supported runtime flags for the MCP server:

- --profile-path <path>: use the Profile Path from chrome://version (auto-derives user data dir + profile name)
- --user-data-dir <path>: reuse a Chrome profile directory for persistent sessions
- --profile-directory <name>: select a profile within the user data dir
- --chrome-path <path>: explicit path to the Chrome/Chromium executable (overrides auto-detection; also respects the CHROME_PATH environment variable)
- --chrome-flag <flag> or --chrome-flag=<flag>: pass through extra Chrome flags (repeatable)
- --chrome-port <port> or --remote-debugging-port <port>: attach to an existing Chrome instance launched with remote debugging enabled
- --headless: force headless mode
- --no-headless: force headed mode

WSL2 / Custom Chrome Path

If the wrong Chrome binary is picked up (e.g. Windows Chrome instead of the Linux binary on WSL2), set the path explicitly:

```bash