How do I connect Pagespeed Insights MCP Server to Claude?

Run `claude mcp add pagespeed-insights-mcp -- npx -y pagespeed-insights-mcp` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.

Is Pagespeed Insights MCP Server free?

The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.

What can Pagespeed Insights MCP Server do?

Pagespeed Insights MCP Server documents 31 tools to the agent, including analyze_page_speed, batch_analyze, categories. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

Pagespeed Insights MCP

Unclaimed

by ruslanlap

Six-tool MCP server for Google PageSpeed Insights & Chrome UX Report APIs. Analyze, compare, and optimize web performance directly through Claude, Cursor, or any MCP-compatible AI client.

Set up this server

Compare servers My Stack

01 / Choose your client

02 / Before you connect

Authentication is not specified. Check the project instructions before connecting.

Install the runtime required by the project and make it available to your client.

Project instructionsEnvironment variable names (optional)

Use names from the project instructions, separated by commas. Enter names only, never secret values.

03 / Add the configuration

Source: generated from public install instructions

claude mcp add --transport stdio 'pagespeed-insights-mcp' -- 'npx' '-y' 'pagespeed-insights-mcp'

Run in your terminal after replacing any placeholders.

04 / Check it in your client

Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.

claudeclaude-codeclaude-desktopcodexcore-web-vitalscursorgeminigoogle-insightslighthousemcpmcp-servermcp-serverspagespeed-insightsseoseo-optimizationweb-performance

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

31 of 31 tools

Documented tools (31)

From project documentation. A server handshake does not verify each tool’s description or behavior.

analyze_page_speed

Full Lighthouse analysis — all metrics and audits

batch_analyze

Analyze up to 10 URLs in parallel with progress tracking

clear_cache

Clear internal cache to force fresh API requests

compare_pages

Side-by-side performance comparison between two URLs

crux_summary

Real-world Core Web Vitals from Chrome UX Report (field data)

formFactor

"PHONE", "DESKTOP", or "TABLET" (default: "PHONE")

full_report

Run pagespeedanalyzepage and pagespeedgetfielddata; lab and field data stay explicit rather than being mixed.

get_element_analysis

LCP/CLS DOM elements causing performance issues

get_full_audit

Complete Lighthouse audit for all categories

get_image_optimization_details

Images needing optimization with exact savings

get_javascript_analysis

JS bootup time, main-thread work, unused & duplicated modules

get_network_analysis

Network waterfall — all requests with timing and size

get_origin_crux

Domain-level (origin) Chrome UX Report field data across all pages

get_performance_map

Mermaid flowchart visualizing performance score, Core Web Vitals status, and top opportunities

get_performance_summary

Simplified key-metrics report

get_recommendations

Prioritized recommendations with actionable fixes

get_render_blocking_details

Render-blocking resources and critical request chains

get_third_party_impact

Third-party script impact grouped by provider

get_visual_analysis

Screenshots, filmstrip, and full-page captures

pagespeed_analyze_batch

Triage 1–10 pages with progress notifications when supported.

pagespeed_analyze_page

One-page Lighthouse health check, full report, recommendations, audit findings, or a Mermaid map (report).

pagespeed_clear_cache

Clear this process's in-memory API cache after a deploy.

pagespeed_compare_pages

Compare two pages now, or compare one page with its saved baseline (mode).

pagespeed_diagnose_page

One focused investigation: visual, elements, network, javascript, images, render-blocking, or third-parties.

pagespeed_get_field_data

CrUX real-user Core Web Vitals for a page or origin.

strategy

"mobile" or "desktop" (default: "mobile")

urlA

(required): First URL to compare

urlB

(required): Second URL to compare

urls

(required): Array of URLs to analyze (max 10)

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Pagespeed Insights MCP Server

How do I connect Pagespeed Insights MCP Server to Claude?: Run `claude mcp add pagespeed-insights-mcp -- npx -y pagespeed-insights-mcp` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
Is Pagespeed Insights MCP Server free?: The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Pagespeed Insights MCP Server do?: Pagespeed Insights MCP Server documents 31 tools to the agent, including analyze_page_speed, batch_analyze, categories. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.