Playwright MCP Server 🎭

Created By
executeautomationa year ago
Playwright Model Context Protocol Server - Tool to automate Browsers and APIs in Claude Desktop, Cline, Cursor IDE and More 🔌
Overview

what is Playwright MCP Server?

Playwright MCP Server is a Model Context Protocol server that integrates Playwright for browser automation, allowing LLMs to interact with web pages, capture screenshots, and execute JavaScript inside a real browser environment.

how to use Playwright MCP Server?

To use Playwright MCP Server, install the package via npm or mcp-get, and configure it with your desired settings to begin automating web interactions.

key features of Playwright MCP Server?

  • Automated navigation to websites
  • Screenshot capture of entire pages or specific elements
  • Executing JavaScript code in the browser context
  • Interaction with web elements through clicking, hovering, and filling forms
  • Access to browser console logs for debugging purposes

use cases of Playwright MCP Server?

  1. Automating web testing for applications
  2. Monitoring browser logs and capturing issues in real-time
  3. Generating screenshots for documentation or reporting purposes
  4. Executing complex JavaScript functions to manipulate page behavior

FAQ from Playwright MCP Server?

  • How do I install Playwright MCP Server?

You can install it using npm with the command npm install -g @executeautomation/playwright-mcp-server or through mcp-get.

  • What is the benefit of using Playwright MCP Server?

It facilitates automation tasks by allowing LLMs to control browsers programmatically, useful for testing, scraping, and interactive automation applications.

  • Can I build the server from source?

Yes! You can clone the repository and follow the build instructions provided in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
executeautomation
Star
3778
Language
TypeScript
License
MIT license
Tags

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)

20 hours ago
Gpt Scrambler

2 days ago