PageSpeed Insights MCP

Install

Works with Claude Desktop. Read the repository before you give any tool access to your data.

About

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 26, 2026.

Tools

6 read · 0 write · 0 deleteRead-only

Secrets

None asked for

Install scripts

Runs code on install

Runs as

Downloaded binary

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+…].

• analyse_page

  Use to measure a page in the lab and find what to fix (scores with their spread, failing audits ranked by what fixing them is worth, real-user data beside them, and a page to send on); for real-user data alone use get_field_data, which is fast, and for "did that change help" use compare_to_baseline. include picks the parts, "scores", "issues", "field_data" and "html", default all four. ONE MEASUREMENT SERVES EVERY PART, so asking for more costs no extra API calls, while asking in separate calls measures again. SLOW, several minutes. It reports the MEDIAN of several DISTINCT analyses with the m…

• check_setup

  Use first when anything looks wrong, to tell a configuration problem apart from a slow or failing page before committing to a full check. Reports what is configured and what actually works right now (key present, PageSpeed reachable, Chrome UX Report permitted) without disclosing the key.

• compare_to_baseline

  Use to answer "did that change actually help"; for a one-off measurement with nothing to compare against use analyse_page. Measures now and compares against a saved baseline for the same URL and strategy. THE FIRST CALL ON A URL RECORDS THE BASELINE and compares nothing, which is the correct answer before anything has changed, and a call after the change compares against it. A verdict is only given where the two min-max ranges do NOT overlap: on an unchanged page the performance score has been measured running 27 to 37 and Total Blocking Time 824ms to 3.05s, so comparing medians alone reports …

• explain_lcp

  Use when Largest Contentful Paint is the problem, to find which part of the load owns it; for the LCP figure alone use get_field_data, and for lab scores and what to fix use analyse_page. Breaks a slow LCP into the four phases it is made of: server response, then the delay before the browser starts fetching the largest image, then the download, then the delay before it is painted. FAST, one Chrome UX Report call, no Lighthouse runs and no noise to average away. TWO THINGS NOT TO GET WRONG, both reported in the output: the phases are each a separate 75th percentile so they do NOT sum to the LCP…

• get_field_data

  Use for what real Chrome users actually experienced, with no lab measurement, so it answers in seconds rather than minutes; for lab scores and what to fix use analyse_page, and for which phase owns a slow LCP use explain_lcp. From the Chrome UX Report, the only evidence here about real visitors and the only thing Google ranks on. Set history for the weekly p75 time series, which shows whether a site has been getting slower for real people over months. Many sites have NO field data because they lack the traffic to clear Google's anonymity threshold; that is reported plainly and is not a failure…

• get_job_result

  Use to collect a measurement that analyse_page or compare_to_baseline handed back as a job id, calling it about every 15 seconds until it reports done. Anything longer than about a minute cannot be answered inside one tool call (clients enforce a hard wall-clock limit and progress notifications do not extend it), so those tools return a job id and keep working. When done it returns exactly what the tool would have returned. ALWAYS answers immediately. Omit job_id for the most recent job. Starting the same measurement again while one is running does not make it arrive any sooner, because the wa…

Signals

Stars

1

Forks

0

Open issues

0

Last commit

Oct 23, 2026 (7 days ago)

Last release

Oct 23, 2026 (7 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

com.considus/pagespeed-insights-mcp

Version

2.0.1

Auth

No auth

Packages

mcpb https://github.com/Considus/pagespeed-insights-mcp/releases/download/v2.0.1/pagespeed-insights-mcp-2.0.1.mcpb

License

Apache-2.0

Repository

github.com/Considus/pagespeed-insights-mcp

Website

considus.com/pagespeed-insights-mcp/

First seen

Oct 24, 2026

Last checked

Oct 25, 2026

Source

Official MCP Registrygithub-graphql