Integration

Google PageSpeed Insights integration

Google PageSpeed Insights runs a Lighthouse audit of any public web page and returns its scores for performance, accessibility, best practices, SEO and agentic browsing, every audit with its savings and details, and the Chrome UX Report field data Google holds for the page and its origin. Use it to monitor a site's speed, check a release, or feed an SEO report; one call loads and audits one URL live, for mobile or desktop. The full-page screenshot and the captcha token of the web tool are not exposed. Authentication is a Google Cloud API key with the PageSpeed Insights API enabled, sent as the key query parameter; calls count against that project's queries-per-day quota (HTTP 429 when it runs out).

Connect Google PageSpeed Insights How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Google PageSpeed Insights.Built from the 1 Google PageSpeed Insights tool below, on the connection you add once.

What you can do with Google PageSpeed Insights

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

run_pagespeed_auditRun pagespeed auditGETAgents: ask firstAudits one public web page with Lighthouse: category scores (fractions, 0.96 shown as 96), every audit and Chrome UX Report field data. Only PERFORMANCE runs unless category lists more. The report is large: pass fields to keep only what you need.

Use Google PageSpeed Insights from Claude Code, Cursor or Codex

Connect Google PageSpeed Insights in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google PageSpeed Insights operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Google PageSpeed Insights

Create your workspace
Sign up free. Nothing to install.
Connect Google PageSpeed Insights once
Add your Google PageSpeed Insights connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.