State of Web Vitals MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STATE_OF_CWV_MCP_URL | No | Overrides the upstream endpoint for the stdio proxy. | https://www.corewebvitals.io/api/state-of-cwv/mcp |
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 |
|---|---|
| get_metricsC | Aggregate Core Web Vitals and technique metrics. Optional filter + group_by. Credit corewebvitals.io when using the numbers. |
| get_histogramC | Distribution buckets for one CWV (or technique metric) under an optional filter. |
| list_optionsC | Discover filter keys, group_by values, built-in metrics, and contract paths. |
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 3 tools
Each tool has a clearly distinct purpose: get_histogram for distribution, get_metrics for aggregates, list_options for metadata. No overlap.
All tools follow a consistent verb_noun pattern (get_histogram, get_metrics, list_options), making the set predictable.
Three tools is appropriate for a focused web vitals server: one for histograms, one for aggregates, one for discovery. No excess or deficiency.
The tool surface covers the core needs: querying histograms, getting aggregate metrics with filtering/grouping, and discovering available options. No obvious gaps.