Lighthouse Audit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PSI_API_KEY | No | Google PageSpeed Insights API key. Without it, the server starts but audits return SERVICE_UNAVAILABLE. | |
| PSI_TIMEOUT_MS | No | Optional PageSpeed Insights request timeout in milliseconds. Defaults to 57000. |
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 |
|---|---|
| run_lighthouseA | Run a fresh Lighthouse lab audit of one public HTTP(S) page using Google PageSpeed Insights. Use for website speed and performance testing, accessibility checks, and basic on-page SEO checks. Returns performance, accessibility, best-practices and SEO scores, lab metrics, and audit findings. Defaults to mobile and can take up to about a minute. The URL is sent to Google. No separate signup or user-provided API key is required. Private or authenticated pages and whole-site crawls are unsupported. No audit history is retained. |
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 1 tool
There is only one tool, so there is no possibility of misselection or overlap. Its purpose (run a Lighthouse audit via PageSpeed Insights) is clearly stated and distinct by definition.
A single tool named run_lighthouse follows a clear verb_noun convention. With only one tool there is no possibility of inconsistent naming patterns.
The server is focused on one narrow capability, but a single tool makes for a thin surface with no alternatives or complementary operations. It is borderline appropriate for the scope rather than well-scoped.
The core audit operation is covered, but notable lifecycle gaps exist: no audit history, no result retrieval/comparison, no desktop toggle surfaced in the tool list, and whole-site or authenticated pages are explicitly unsupported. Agents can perform a one-off audit but cannot persist or compare results.