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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_auditB | Run a comprehensive Lighthouse audit on a website |
| get_accessibility_scoreB | Get the accessibility score and recommendations for a website |
| get_seo_analysisC | Get SEO analysis and recommendations for a website |
| get_performance_scoreC | Get the performance score for a website |
| get_core_web_vitalsA | Get Core Web Vitals metrics for a website |
| compare_mobile_desktopA | Compare website performance between mobile and desktop devices |
| check_performance_budgetB | Check if website performance meets specified budget thresholds |
| get_lcp_opportunitiesB | Get LCP optimization opportunities for a website |
| find_unused_javascriptB | Find unused JavaScript code to reduce bundle size |
| analyze_resourcesA | Analyze website resources (images, JS, CSS, fonts) for optimization opportunities |
| get_security_auditA | Perform security audit checking HTTPS, CSP, and other security measures |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-audit-results | |
| create-performance-plan | |
| compare-audits | |
| seo-recommendations | |
| accessibility-guide | |
| create-performance-budget | |
| optimize-core-web-vitals | |
| optimize-resources |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| core-web-vitals-thresholds | |
| optimization-techniques | |
| wcag-guidelines | |
| seo-best-practices | |
| security-best-practices | |
| budget-guidelines | |
| categories-scoring | |
| framework-guides |
TDQS
Scored across 11 tools
There is significant overlap between run_audit and the specific getter tools (accessibility, SEO, performance), as run_audit likely encompasses all of those. Additionally, get_lcp_opportunities, find_unused_javascript, and analyze_resources all target performance optimization with unclear boundaries.
Most tools follow a clear verb_noun pattern (e.g., get_*, run_audit, compare_mobile_desktop, check_performance_budget). Minor deviations include run_audit vs. get_security_audit (both use 'audit' but different verbs) and find_unused_javascript/analyze_resources not using 'get_' prefix, but the overall convention is consistent.
With 11 tools, the set is well-scoped for a website auditing server. Each tool covers a distinct aspect of Lighthouse auditing (performance, SEO, accessibility, security, resources), and the count is within the ideal 3-15 range without feeling bloated.
The tool surface covers major Lighthouse categories (performance, accessibility, SEO, security, Core Web Vitals, resources) and includes useful extras like budget checks and mobile/desktop comparison. However, it lacks explicit best practices and PWA audits, which are standard Lighthouse categories, creating minor gaps.