Lighthouse Mcp

Created By
priyankarka year ago
Allows AI assistants such as Cursor/Cline/GitHub Copilot to use Google's lighthouse tool to measure perf metrics for your webpage. You can then run an agentic loop and get the assistants to optimize those metrics!
Overview

What is Lighthouse MCP?

Lighthouse MCP is a server that integrates with Google's Lighthouse tool to measure performance metrics for web pages, allowing AI assistants to optimize these metrics.

How to use Lighthouse MCP?

You can use Lighthouse MCP by running it via npx or installing it globally. After configuration, you can run audits on any URL to get performance scores.

Key features of Lighthouse MCP?

  • Comprehensive Lighthouse audits on any URL
  • Performance scores and metrics
  • Device emulation (mobile/desktop)
  • Network throttling control
  • Selection of specific audit categories

Use cases of Lighthouse MCP?

  1. Measuring and optimizing webpage performance for SEO.
  2. Running audits to improve accessibility and best practices.
  3. Integrating with AI assistants for automated performance analysis.

FAQ from Lighthouse MCP?

  • Can I run audits on any website?

Yes! You can run audits on any publicly accessible URL.

  • Is there a specific Node.js version required?

Yes, Node.js version 16 or higher is required.

  • How do I configure the MCP settings?

You can configure the MCP settings by adding the appropriate command and arguments to your configuration file.

Server Config

{
  "mcpServers": {
    "lighthouse": {
      "command": "npx",
      "args": [
        "lighthouse-mcp"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
priyankark
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago