Core Web Vitals and Lighthouse, as one MCP tool through Apify
{ "mcpServers": { "io.github.bepolabs-pagespeed": { "url": "https://mcp.apify.com?tools=bepolabs/pagespeed", "headers": {} } }}Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://mcp.apify.com?tools=bepolabs/pagespeedThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http io.github.bepolabs-pagespeed https://mcp.apify.com?tools=bepolabs/pagespeedRun in a terminal.
{ "mcpServers": { "io.github.bepolabs-pagespeed": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.apify.com?tools=bepolabs/pagespeed" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchTools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Bulk PageSpeed Insights: Core Web Vitals And Lighthouse is reached over HTTP.
Last checked 2026-11-16. Core Web Vitals and Lighthouse, as one MCP tool through Apify
From the publisher
README is not crawled yet. No repository on file.
Core Web Vitals and Lighthouse, as one MCP tool through Apify