Playwright MCP Server - NixOS Flake

Created By
benjaminkitta year ago
A comprehensive NixOS Flake development environment for the Playwright MCP (Model Context Protocol) server with full Chrome and Firefox support, including persistent browser profiles.
Overview

What is Playwright MCP Server?

Playwright MCP Server is a comprehensive NixOS Flake development environment designed for the Playwright Model Context Protocol (MCP) server, providing full support for Chrome and Firefox browsers, including persistent browser profiles.

How to use Playwright MCP Server?

To use the Playwright MCP Server, clone the repository, enable direnv, and the environment will automatically activate. You can also manually activate the development shell or run the MCP server directly using provided commands.

Key features of Playwright MCP Server?

  • Complete Playwright MCP Server setup based on Microsoft's official implementation.
  • Multi-browser support for both Chrome/Chromium and Firefox.
  • Profile persistence to maintain browser profiles between sessions.
  • Desktop profile integration to import existing browser profiles.
  • Properly configured for NixOS with all dependencies included.
  • Ready-to-use development shell with all necessary tools.
  • Compatibility with AI agents for development environments.

Use cases of Playwright MCP Server?

  1. Setting up a development environment for automated browser testing.
  2. Running headless browser tests for web applications.
  3. Importing existing browser profiles for testing purposes.
  4. Integrating with AI development environments for enhanced automation.

FAQ from Playwright MCP Server?

  • Can I use my existing browser profiles?

Yes! You can import your existing Chrome and Firefox profiles into the Playwright MCP Server.

  • Is there support for both Chrome and Firefox?

Yes! The server supports both Chrome/Chromium and Firefox browsers.

  • How do I run the server in headless mode?

You can run the server in headless mode by using the command: playwright-mcp-wrapped --headless.

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