Log inSubmit server
Pagespeed Insights MCP logo

Pagespeed Insights MCP

Audits web performance with Lighthouse and CrUX data, page comparisons, diagnostics, batch analysis, and cached results.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Pagespeed Insights MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "pagespeed-insights-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "pagespeed-insights-mcp"
      ],
      "env": {
        "GOOGLE_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 6 tools correctly (1d ago).

Overview

pagespeed-insights-mcp connects AI clients to Google PageSpeed Insights and Chrome UX Report APIs through MCP. Its tools cover Lighthouse page audits, focused investigations, real-user Core Web Vitals, page comparisons, batch triage, and cache clearing. Use it when an agent needs to inspect performance issues, compare releases or URLs, or turn audit findings into prioritized recommendations.

Use cases

  • Audit a page's Lighthouse performance and collect prioritized fixes
  • Investigate network, JavaScript, image, or third-party bottlenecks
  • Compare pages or check a page against a saved performance baseline
  • Review real-user Core Web Vitals for a page or origin
  • Triage up to ten URLs after a deployment

Key features

  • Lighthouse page analysis with recommendations and audit findings
  • Focused performance diagnostics across seven investigation areas
  • CrUX field data for pages and origins
  • Current and baseline page comparisons
  • Batch analysis for one to ten pages
  • In-memory cache clearing

Tools6

What Pagespeed Insights MCP lets your agent do. Expand a tool for its parameters.

Verified live~1.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 41d

What it can do

From the 6 tools this server returned when we ran it; 6 declare their own safety hints.

Can delete or modify data · 1Makes network requests · 5Read-only tools · 5
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age421 days
Maintainers1

Observed 2026-10-24 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · pagespeed-insights-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars76Stargazers on the source repository.
npm downloads3.5kPackage downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed6Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Pagespeed Insights MCP works

What pagespeed-insights-mcp does

pagespeed-insights-mcp exposes Google PageSpeed Insights and Chrome UX Report capabilities to MCP-compatible AI clients. It combines Lighthouse lab analysis with CrUX field data, allowing an agent to examine both a controlled performance run and real-user Core Web Vitals for a page or origin.

The server is suited to performance reviews that need more than a single score. It can return audit findings, recommendations, screenshots-based visual analysis, focused diagnostic views, comparisons, batch results, and saved-baseline comparisons. Its tools are useful for investigating regressions after a deployment, reviewing several URLs, or identifying concrete optimization work.

How it works

The server runs as a local stdio process and communicates with the MCP client. A Google API key is passed through the process environment, and requests are made to the PageSpeed Insights and CrUX APIs. Repeated requests can use the process's in-memory cache; the cache can be cleared after a deployment with the dedicated cache tool.

Lighthouse analysis can be requested for a single page, while focused diagnosis narrows the investigation to visual output, page elements, network activity, JavaScript, images, render-blocking resources, or third-party code. CrUX queries accept either a page or an origin. Comparison requests can compare two current pages or compare a page with its stored baseline. Batch analysis handles between one and ten pages and can report progress when the connected client supports notifications.

Setup and configuration

Install and launch the package with npx from the MCP client's server configuration. The process requires the GOOGLE_API_KEY environment variable, which should contain a Google API key obtained through Google Cloud's PageSpeed Insights setup. A minimal configuration uses the pagespeed-insights-mcp package as the command's argument and passes the key in env.

Claude Desktop configuration uses claude_desktop_config.json. Codex/OpenAI configurations use TOML. The documented client configurations also install pino-pretty alongside the server with npx for log formatting. After changing the configuration, restart the client and verify that the server is running before invoking its tools.

Tools and capabilities

  • Analyze one page with a Lighthouse health check, full report, recommendations, audit findings, or a Mermaid map.
  • Diagnose one performance area, including visual output, elements, network, JavaScript, images, render-blocking resources, or third parties.
  • Retrieve CrUX real-user Core Web Vitals for a page or origin.
  • Compare two pages or compare a page against a saved baseline.
  • Analyze one to ten pages in a batch with progress notifications where supported.
  • Clear the process-local in-memory API cache after a deployment.

Limitations and notes

Lighthouse results represent lab runs and can vary between requests; using multiple runs can help produce a more representative median. CrUX data describes real-user experience and is distinct from Lighthouse's controlled test conditions. Batch progress depends on MCP client notification support. API access also depends on a valid Google API key and the availability of data for the requested page or origin.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Pagespeed Insights MCP

pagespeed-insights-mcp is an MCP server that connects AI clients to Google's PageSpeed Insights and Chrome UX Report APIs. Its main tools analyze pages with Lighthouse, diagnose performance areas, retrieve CrUX Core Web Vitals, compare pages or baselines, analyze batches of URLs, and clear the process cache.

Install it through an MCP client's stdio configuration with `npx -y pagespeed-insights-mcp`. Set `GOOGLE_API_KEY` in the server's environment, then restart the client. Claude Desktop uses `claude_desktop_config.json`, while Codex/OpenAI uses a TOML configuration.

It requires a Google API key in the `GOOGLE_API_KEY` environment variable. The key is used to access Google's PageSpeed Insights and Chrome UX Report APIs, and the configuration examples obtain it through Google Cloud's PageSpeed Insights setup.

Yes. `pagespeed_compare_pages` can compare two pages in the current run or compare one page with its saved baseline. This supports checking for performance changes after a deployment.

Yes. Cursor is named as a supported MCP client, and the server uses a standard local stdio configuration. It can also be used with Claude Desktop, Codex/OpenAI configurations, and other MCP-compatible clients.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPagespeed Insights MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/pagespeed-insights-mcp-2?style=directory)](https://allmcps.com/mcp/pagespeed-insights-mcp-2)
HTML Embed
<a href="https://allmcps.com/mcp/pagespeed-insights-mcp-2"><img src="https://allmcps.com/api/badge/pagespeed-insights-mcp-2?style=directory" alt="Pagespeed Insights MCP on AllMCPs" /></a>