lighthouse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_urlA | Run a Lighthouse performance audit on a URL. Returns Core Web Vitals (LCP, CLS, INP), other performance metrics (FCP, TTFB, Speed Index, TBT), category scores (0-100), and a prioritized list of improvement opportunities with estimated savings. |
| audit_batchA | Run Lighthouse performance audits on multiple URLs in parallel. Returns a summary comparing Core Web Vitals across all URLs, plus detailed metrics for each. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are clearly distinct: audit_url handles a single URL while audit_batch handles multiple URLs. There is no overlap or ambiguity in their purposes.
Both tools use the consistent verb_noun pattern (audit_url, audit_batch), making the naming predictable and easy to follow.
With only 2 tools, the server feels thin for a full-featured Lighthouse server, though the tools cover the core audit functionality. It is below the typical 3-15 range.
The tools cover both single and batch audits, returning comprehensive metrics and opportunities. Minor gaps include lack of custom configuration options (e.g., device, categories) or historical comparison, but these are not critical.