Playwright MCP Docker Environment

Created By
iuilla year ago
This project provides a Docker Compose environment to run the '@playwright/mcp' server.
Overview

What is Playwright MCP Docker Environment?

Playwright MCP Docker Environment is a project that provides a Docker Compose setup to run the '@playwright/mcp' server, facilitating easy management and deployment of the Playwright MCP server for various clients.

How to use Playwright MCP Docker Environment?

To use this project, clone the repository, create and configure a .env file, and then build and start the Docker container using Docker Compose commands.

Key features of Playwright MCP Docker Environment?

  • Easy setup with Docker Compose for the Playwright MCP server.
  • Configuration options for headless and headed modes.
  • Support for various client configurations like VSCode and Cline.

Use cases of Playwright MCP Docker Environment?

  1. Running automated tests in a headless browser environment.
  2. Integrating with development tools for real-time feedback.
  3. Facilitating browser automation tasks in a controlled environment.

FAQ from Playwright MCP Docker Environment?

  • What are the prerequisites for using this project?

You need Docker and Docker Compose installed on your machine.

  • How do I switch between headless and headed modes?

You can switch modes by changing the HEADLESS variable in the .env file and restarting the container.

  • Can I use this project on Windows?

Yes, but ensure that your WSL or X Server settings are correctly configured for GUI applications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
iuill
Star
0
Language
Shell
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