Install playwright-mcp with Homebrew, Nix

Project links

• Homepage
• Package manager page

Commands and aliases

• playwright-mcp

Project history

Microsoft created the dedicated playwright-mcp repository in March 2025 as the official Playwright server for the Model Context Protocol. It builds on Playwright's cross-browser automation and presents browser operations as structured tools for language-model agents.

The official project subsequently expanded beyond core navigation and interaction to cover configurable capabilities, isolated or persistent browser profiles, HTTP transport, network and storage tools, screenshots, code execution, and browser-extension attachment.

Adoption history

Official setup guidance documents Playwright MCP with VS Code, Cursor, Claude Code, Claude Desktop, Codex, and other MCP clients. A standard command-based server definition makes it portable across clients supporting local MCP servers.

The project adopted accessibility snapshots as its primary agent interface, avoiding a mandatory vision model while still offering screenshots and optional capabilities for storage, testing, network inspection, PDF handling, and developer tools.

How it is used

Configure an MCP client to launch `playwright-mcp` or the equivalent package command, then ask the client to navigate and interact with pages. The server returns accessibility-tree snapshots with stable references for subsequent tool calls.

Advanced settings may be supplied through a user-chosen configuration file, environment variables, or command-line arguments. Secret dotenv files and storage-state files are also explicitly user-selected, so the project does not define one universal credentials-file location.

Why package nerds care

Playwright MCP is a prominent example of browser automation being repackaged as an MCP server rather than only as a test library. Package users care about the boundary between the server, the MCP client's configuration, browser binaries, persisted profiles, and optional secret or storage-state files.

Its capability system is also packaging-relevant: deployments can limit exposed tool schemas to reduce context cost and constrain the server to the functions required by a workflow.

Timeline

• 2025: Microsoft created the dedicated playwright-mcp repository.
• 2025 onward: The project shipped frequent official releases as MCP client integrations and browser capabilities expanded.

Related projects

• Playwright supplies the underlying browser automation.
• Playwright CLI offers an official shell-command and skills-oriented interface to related agent automation workflows.
• The Model Context Protocol defines the client-server integration used to expose the browser tools.

Sources

• https://api.github.com/repos/microsoft/playwright-mcp
• https://github.com/microsoft/playwright-mcp
• https://playwright.dev/mcp/capabilities
• https://playwright.dev/mcp/configuration/options
• https://playwright.dev/mcp/introduction