Playwright-Lighthouse MCP Server

Created By
kbyk004a year ago
A MCP server that analyzes web site performance using Playwright and Lighthouse.
Overview

What is Playwright-Lighthouse MCP Server?

Playwright-Lighthouse MCP Server is a server that analyzes website performance using Playwright and Lighthouse through the Model Context Protocol (MCP).

How to use Playwright-Lighthouse MCP Server?

To use the server, clone the repository, install the dependencies, and run the server with the appropriate configuration for MCP clients.

Key features of Playwright-Lighthouse MCP Server?

  • Performance analysis using Lighthouse
  • Screenshot capture of web pages
  • Integration with MCP clients like Claude for Desktop

Use cases of Playwright-Lighthouse MCP Server?

  1. Analyzing the performance of web applications.
  2. Capturing screenshots for visual regression testing.
  3. Integrating with other tools that support the Model Context Protocol.

FAQ from Playwright-Lighthouse MCP Server?

  • What are the prerequisites for using this server?

You need Node.js 18 or higher and npm installed.

  • Can I integrate this server with other applications?

Yes! It can be integrated with any client that supports the Model Context Protocol (MCP).

  • What kind of analysis does it perform?

It performs performance analysis and can capture screenshots of web pages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kbyk004
Star
0
Language
TypeScript
License
MIT 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