
by ruslanlap
PageSpeed Insights MCP is a six-tool MCP server for the Google PageSpeed Insights and Chrome UX Report APIs. It lets Claude, Cursor or another MCP client analyze, compare and track web performance.
PluginContact for pricing
Step 1: Get a free API key from Google Cloud Console.
Step 2: Add a pagespeed-insights server to your client config, such as claude_desktop_config.json, running npx with pagespeed-insights-mcp.
Step 3: Set GOOGLE_API_KEY in the server's env block.
Step 4: Restart the client so it loads the server.
Step 5: Ask for a performance audit of a URL, or use the /performance-audit prompt.
Step 6: Use runs of 3 to 5 for medians, since a single Lighthouse run is noisy.
Six workflow tools named pagespeed_*, such as pagespeed_analyze_page and pagespeed_get_field_data. They cover analysis, field data, audits, comparison and baselines.
Yes, a Google API key supplied as GOOGLE_API_KEY. The README says you can get one free in Google Cloud Console.
Lighthouse lab data comes from a throttled test run, while CrUX field data reflects real Chrome users. The server returns both.
Requirements
YawLabs Redis MCPAn MCP server from Yaw Labs for exploring and diagnosing Redis and Valkey instances from an MCP client. It is read-only by default and always enumerates keys with SCAN.
CRAPKit MCPcrapkit scores every function in a repository by complexity times uncovered risk, ranks the worst, and blocks commits that add more. An optional MCP server lets coding agents use its JSON output.