Run Google Lighthouse on public page URLs for performance, accessibility, best-practices and SEO
{ "mcpServers": { "io.github.kriton-dev-lighthouse-audit": { "url": "https://mcp.apify.com/?tools=hermeskd/lighthouse-audit", "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=hermeskd/lighthouse-auditThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http io.github.kriton-dev-lighthouse-audit https://mcp.apify.com/?tools=hermeskd/lighthouse-auditRun in a terminal.
{ "mcpServers": { "io.github.kriton-dev-lighthouse-audit": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.apify.com/?tools=hermeskd/lighthouse-audit" ] } }}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.
Lighthouse — Mobile/Desktop Lab Audits, Scores & Fix Hints is reached over HTTP.
Last checked 2026-11-18. Run Google Lighthouse on public page URLs for performance, accessibility, best-practices and SEO
From the publisher
README is not crawled yet. No repository on file.
Run Google Lighthouse on public page URLs for performance, accessibility, best-practices and SEO