MCP Lighthouse Audit
by jladev
README.md
# MCP Lighthouse Audit
An MCP server that provides detailed Lighthouse audits for web pages. Unlike basic tools that only return scores, this server returns the specific elements that fail each audit with actionable suggestions.
## Features
- Detailed Lighthouse audits with scores and specific failing elements
- Works with localhost and public URLs
- Desktop and mobile presets
- Category filtering (performance, accessibility, seo, best-practices)
- Clear output format with HTML snippets and selectors
## Installation
```bash
# Clone and build
cd ~/Dev/mcp-lighthouse-audit
pnpm install
pnpm build
```
## Add to Claude Code
```bash
claude mcp add lighthouse-audit node ~/Dev/mcp-lighthouse-audit/dist/index.js
```
Or add manually to `~/.claude/settings.json`:
```json
{
"mcpServers": {
"lighthouse-audit": {
"command": "node",
"args": ["/Users/<username>/Dev/mcp-lighthouse-audit/dist/index.js"]
}
}
}
```
## Usage
Once installed, you can use the `audit_page` tool in Claude:
### Basic audit
```
Audit http://localhost:4343/cottages
```
### With specific categories
```
Audit http://localhost:4343 for accessibility only
```
### Mobile preset
```
Audit https://example.com with mobile preset
```
## Tool: audit_page
### Input
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| url | string | Yes | URL to audit (localhost or public) |
| categories | string[] | No | Categories to audit: performance, accessibility, best-practices, seo |
| preset | string | No | Device preset: desktop (default) or mobile |
### Output
Returns a formatted report with:
- Scores for each category (0-100)
- Summary of passed/failed audits
- Detailed list of failed audits grouped by category
- For each failed audit:
- ID and title
- Score
- Description
- Affected elements (HTML snippets, CSS selectors, URLs)
## Requirements
- Node.js >= 18
- Chrome or Chromium installed on the system
## License
MIT
TDQS
A3.7/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion between tools. The purpose is clearly defined as running a Lighthouse audit.
Naming Consistency5/5
The single tool name 'audit_page' follows a clear verb_noun pattern, which is consistent and descriptive.
Tool Count3/5
A single tool for a Lighthouse audit server is functional but feels minimal. The tool is well-scoped, yet the server could benefit from additional related tools (e.g., audit_mobile, compare_audits).
Completeness4/5
The tool covers the core audit action comprehensively, returning all category scores and failed audits. However, there are no supplementary operations like retrieving historical audits or configuring audit options.
Maintenance
ActivityInactive
ResponsivenessNo issues