Lighthouse Audit avatar
Lighthouse Audit

Pricing

$30.00/month + usage

Go to Store
Lighthouse Audit

Lighthouse Audit

Developed by

Caleb David

Caleb David

Maintained by Community

Automatically test the speed of your web pages and get daily or weekly detailed performance reports using Google's Lighthouse for Chrome. Ensure your website remains fast even as you add new features and pages. Export the result in ZIP and MHTML files

0.0 (0)

Pricing

$30.00/month + usage

2

Total users

60

Monthly users

5

Runs succeeded

>99%

Last modified

a year ago

You can access the Lighthouse Audit programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=microworlds/lighthouse-audit",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Lighthouse Audit

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=microworlds/lighthouse-audit along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=microworlds/lighthouse-audit",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.