MCP Server Playwright

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is MCP Server Playwright?

MCP Server Playwright is a Model Context Protocol server that provides browser automation capabilities using Playwright, enabling large language models (LLMs) to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.

How to use MCP Server Playwright?

To use MCP Server Playwright, install it via npm or Smithery, and configure it to integrate with your LLM environment. You can then utilize various commands to navigate, capture screenshots, and interact with web elements.

Key features of MCP Server Playwright?

  • Full browser automation capabilities
  • Screenshot capture of entire pages or specific elements
  • Comprehensive web interaction (navigation, clicking, form filling)
  • Console log monitoring
  • JavaScript execution in browser context

Use cases of MCP Server Playwright?

  1. Automating web testing for applications.
  2. Capturing screenshots for documentation or reporting.
  3. Interacting with web applications for data extraction.

FAQ from MCP Server Playwright?

  • Can MCP Server Playwright be used with any web application?

Yes! It can automate interactions with any web application that is accessible via a browser.

  • Is MCP Server Playwright free to use?

Yes! It is open-source and free to use under the MIT License.

  • What platforms does MCP Server Playwright support?

It supports both Windows and macOS.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
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)

9 hours ago