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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago