测试

Created By
microsofta year ago
Overview

What is Playwright MCP?

Playwright MCP is a Model Context Protocol server that provides browser automation capabilities using Playwright. It allows large language models (LLMs) to interact with web pages through structured accessibility snapshots, eliminating the need for screenshots or visually-tuned models.

How to use Playwright MCP?

To use Playwright MCP, install the server with your preferred client (e.g., VS Code, Cursor). A typical configuration involves using the command npx @playwright/mcp@latest to set up the server.

Key features of Playwright MCP?

  • Fast and lightweight, utilizing Playwright's accessibility tree instead of pixel-based input.
  • LLM-friendly, operating purely on structured data without the need for vision models.
  • Deterministic tool application, reducing ambiguity compared to screenshot-based methods.

Use cases of Playwright MCP?

  1. Automating web interactions for testing and development.
  2. Enabling LLMs to perform tasks on web pages without visual input.
  3. Facilitating browser automation in environments without a display.

FAQ from Playwright MCP?

  • Can Playwright MCP be used with any browser?

Yes, it supports multiple browsers including Chrome, Firefox, and WebKit.

  • Is Playwright MCP free to use?

Yes, it is open-source and free for everyone.

  • What are the system requirements for Playwright MCP?

You need Node.js 18 or newer to run Playwright MCP.

Server Config

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
microsoft
Star
-
Language
-
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)

a day ago