MCP server for PageSpeed & SEO audits. Zero config required - works out of the box.
Connect Pagespeed to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for PageSpeed & SEO audits. Zero config required - works out of the box. The pagespeed mcp server is what makes that connection.
A Model Context Protocol (MCP) server for PageSpeed & SEO audits. Zero configuration required - just install and use.
By day, I'm a martech consultant, working with billion-dollar brands like Rolex and Helsana. By night, I build tools like AI SEO Copilot (15k+ installs), AEO Copilot, and blueprints like Webflow SEO Checklist (1k+ downloads) to help my Webflow friends make money with SEO and AEO.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
run_pagespeed_test — Full PageSpeed Insights API response with all Lighthouse datatechnical_seo_audit — The technical_seo_audit tool exposed by this serversitemap_robots_audit — The sitemap_robots_audit tool exposed by this serveronpage_seo_audit — The onpage_seo_audit tool exposed by this serversecurity_headers_audit — The security_headers_audit tool exposed by this serverperformance_audit — The performance_audit tool exposed by this servermobile_audit — The mobile_audit tool exposed by this serverConfiguration is passed through the environment: PAGESPEED_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pagespeed's toolset — run_pagespeed_test, technical_seo_audit, sitemap_robots_audit and 4 more — is a fair guide to whether it matches your workflow. It is maintained by sofianbettayeb; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Pagespeed's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| run_pagespeed_test | Full PageSpeed Insights API response with all Lighthouse data. |
| technical_seo_audit | The technical_seo_audit tool exposed by this server. |
| sitemap_robots_audit | The sitemap_robots_audit tool exposed by this server. |
| onpage_seo_audit | The onpage_seo_audit tool exposed by this server. |
| security_headers_audit | The security_headers_audit tool exposed by this server. |
| performance_audit | The performance_audit tool exposed by this server. |
| mobile_audit | The mobile_audit tool exposed by this server. |
{
"mcpServers": {
"pagespeed": {
"command": "npx",
"args": ["-y", "pagespeed-mcp-server"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PAGESPEED_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.