Pagespeed Insights MCP

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/ruslanlap-pagespeed-insights-mcp

About

Use cases: frontend-development, seo

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools

4 read · 0 write · 2 delete

Secrets

1 (API keys, tokens or passwords)

Install scripts

None found

Runs as

Node.js package

Tools (6)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• pagespeed_analyze_batchAnalyze Multiple Pagesread-only

  Analyze 1–10 public URLs and return per-page results plus success/failure counts. Use pagespeed_analyze_page for one URL or pagespeed_compare_pages for a direct comparison. Example: triage the ten highest-traffic landing pages. Progress notifications are emitted when supported by the client.

• pagespeed_analyze_pageAnalyze a Page with Lighthouseread-only

  Run a PageSpeed Insights Lighthouse analysis for one public page. Start with report=summary for a health check; choose full for audits, recommendations for a prioritized fix list, audit for non-performance categories, or performance-map for Mermaid. Example: analyze a mobile product page and return the three most useful remediation steps. Returns a report plus structured result. The Google API is contacted and results may be served from the local cache.

• pagespeed_clear_cacheClear Local PageSpeed Cache

  Clear only this server process's in-memory PageSpeed response cache, forcing later analysis calls to contact Google again. Use after a deploy when a cached result is stale. It does not change the target website, files, or remote data; repeating the call is safe.

• pagespeed_compare_pagesCompare Pages or a Stored Baselinecan change or delete data

  Compare two pages now (mode=pages) or measure one page against its locally stored baseline (mode=baseline). Baseline mode records the first call; use runs=3 or more and rely on guaranteed deltas, not medians alone. Example: compare staging against production, or verify whether a deployed fix improved mobile LCP. replaceBaseline overwrites local baseline state.

• pagespeed_diagnose_pageDiagnose a Page Performance Problemread-only

  Inspect one page through exactly one diagnostic lens: visual, elements, network, javascript, images, render-blocking, or third-parties. Use after pagespeed_analyze_page identifies a problem; do not use it for a general score. Example: focus=render-blocking to identify CSS/JS delaying first render. Returns focused evidence rather than a full Lighthouse dump.

• pagespeed_get_field_dataGet Chrome UX Report Field Dataread-only

  Get real-user Core Web Vitals from Chrome UX Report, not Lighthouse lab measurements. Use scope=page for one URL; use scope=origin with a bare origin when the page has insufficient traffic. Example: check mobile LCP and INP for https://example.com/checkout. Returns p75 field metrics or a clear no-data result.

Signals

Stars

75

Forks

11

Open issues

0

Contributors

8

Last commit

Oct 21, 2026 (8 days ago)

Last release

Oct 20, 2026 (9 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.ruslanlap/pagespeed-insights-mcp

Version

2.2.0

Auth

API key

Packages

npm pagespeed-insights-mcp

License

Apache-2.0

Repository

github.com/ruslanlap/pagespeed-insights-mcp

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql