Playwright MCP Server - NixOS Flake
@benjaminkitt
About Playwright MCP Server - NixOS Flake
A comprehensive NixOS Flake development environment for the Playwright MCP (Model Context Protocol) server with full Chrome and Firefox support, including persistent browser profiles.
Basic information
Config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Playwright MCP Server - NixOS Flake?
A NixOS Flake development environment for the Playwright Model Context Protocol (MCP) server, providing complete Chrome/Chromium and Firefox browser support with persistent browser profiles. It wraps Microsoft’s official Playwright MCP server with NixOS-specific configurations for developers who want a reproducible setup on NixOS.
How to use Playwright MCP Server - NixOS Flake?
Clone or copy flake.nix, then activate with direnv allow or manually with nix develop. Run the server using playwright-mcp-wrapped (headed mode by default) or nix run. Use flags such as --headless, --browser firefox, --config /path/to/config.json, or --port 8931 for server mode. Import desktop profiles by running nix run .#setup-profiles.
Key features of Playwright MCP Server - NixOS Flake
- Complete Playwright MCP server setup based on Microsoft’s implementation
- Multi-browser support: Chrome/Chromium and Firefox
- Browser profile persistence between sessions
- Desktop profile integration (import existing profiles)
- Properly configured for NixOS with all dependencies
- Ready-to-use development shell with all tools
- AI agent compatible (can be added as a URL to dev environments)
Use cases of Playwright MCP Server - NixOS Flake
- Running Playwright MCP server on NixOS with persistent browser profiles
- Using browser-automated AI agents that need recurring login state
- Importing existing desktop Chrome or Firefox profiles into Playwright MCP
- Configuring a remote MCP server accessible over a network port
- Adding Playwright MCP as a development environment for Claude Desktop or similar AI tools
FAQ from Playwright MCP Server - NixOS Flake
How does this differ from the upstream Microsoft Playwright MCP server?
This flake wraps the upstream server with NixOS-specific configurations, providing multi-browser support, profile persistence, and a development shell, all managed via Nix.
What browsers are supported and how are they integrated?
Chrome/Chromium and Firefox are included as Nix packages and properly configured for Playwright. You can specify the browser with the --browser flag.
Where are browser profiles stored?
Browser profiles are stored in ~/.local/share/playwright-mcp/ – Chrome/Chromium under chrome-profile and Firefox under firefox-profile.
What if I get a “browser not found” error?
Run nix run .#playwright-mcp -- --browser chromium or set PLAYWRIGHT_BROWSERS_PATH to the Nix-build path for Playwright browsers.
How do I reset or fix profile issues?
Remove the profile directory (~/.local/share/playwright-mcp/) and rerun nix run .#setup-profiles to copy fresh profiles. Ensure the directory is writable with chmod -R u+w.
More Browser Automation MCP servers
App Store Scraper MCP Server
appreply-coThis is an MCP server that provides tools to LLMs for searching and analyzing apps from both Google Play Store and Apple App Store – perfect for ASO.
Webpage Screenshot MCP Server
ananddtyagiAn MCP that gives your agent the ability to snap a screenshot of webpages. Useful when you want your agent to check its progress during development.
Yoyo
firecrawl🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
MCP Browser Kit
ndthanhdevAn MCP Server that enables AI assistants to interact with your local browsers.
Slack Slack
microsoftPlaywright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
Comments