Sandbox
@microsoft/playwright-mcp

Playwright MCP server for browser control

Playwright MCP connects an MCP client to Playwright so an agent can open pages, inspect accessibility trees, and run browser actions. It is built around structured page data, which keeps it usable for text-first agents and avoids relying on screenshots.

36,983 stars3.1k forksTypeScriptUpdated 7d ago
Who it's for

Builders who want their agent to interact with live web pages, log in, click through flows, and verify browser behavior.

What it delivers

You can let an agent drive real browsers for browsing, testing, and web workflows from your MCP client.

What it does

Structured browser snapshots

Uses Playwright accessibility trees instead of screenshots, so the agent sees page structure as text.

Browser automation actions

Lets the agent navigate pages, click elements, fill forms, and inspect content through Playwright.

Persistent or isolated sessions

Supports saved browser profiles, isolated test sessions, and connecting to an existing browser.

Client-specific setup commands

Provides install commands and config examples for Claude Code, Codex, Cursor, VS Code, Gemini CLI, Windsurf, and others.

Configurable browser behavior

Supports browser choice, timeouts, storage state, permissions, proxies, viewport size, and other runtime options.

How to get it

  1. 1Add via the amp mcp add command below
    amp mcp add playwright -- npx @playwright/mcp@latest
  2. 2Use the Claude Code CLI to add the Playwright MCP server
    claude mcp add playwright npx @playwright/mcp@latest
  3. 3Use the Codex CLI to add the Playwright MCP server
    codex mcp add playwright npx "@playwright/mcp@latest"
  4. 4Use the Copilot CLI to interactively add the Playwright MCP server
    /mcp add
  5. 5Use the Factory CLI to add the Playwright MCP server
    droid mcp add playwright "npx @playwright/mcp@latest"
  6. 6Use the Grok CLI to add the Playwright MCP server
    grok mcp add playwright -- npx @playwright/mcp@latest

README

Playwright MCP

A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models.

Playwright MCP vs Playwright CLI

This package provides MCP interface into Playwright. If you are using a coding agent, you might benefit from using the CLI+SKILLS instead.

  • CLI: Modern coding agents increasingly favor CLI–based workflows exposed as SKILLs over MCP because CLI invocations are more token-efficient: they avoid loading large tool schemas and verbose accessibility trees into the model context, allowing agents to act through concise, purpose-built commands. This makes CLI + SKILLs better suited for high-throughput coding agents that must balance browser automation with large codebases, tests, and reasoning within limited context windows.
    Learn more about Playwright CLI with SKILLS.

  • MCP: MCP remains relevant for specialized agentic loops that benefit from persistent state, rich introspection, and iterative reasoning over page structure, such as exploratory automation, self-healing tests, or long-running autonomous workflows where maintaining continuous browser context outweighs token cost concerns.

Key Features

  • Fast and lightweight. Uses Playwright's accessibility tree, not pixel-based input.
  • LLM-friendly. No vision models needed, operates purely on structured data.
  • Deterministic tool application. Avoids ambiguity common with screenshot-based approaches.

Requirements

  • Node.js 18 or newer
  • VS Code, Cursor, Windsurf, Claude Desktop, Goose, Grok, Junie or any other MCP client

Getting started

First, install the Playwright MCP server with your client.

Standard config works in most of the tools:

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest"
      ]
    }
  }
}

Install in VS Code Install in VS Code Insiders

Amp

Add via the Amp VS Code extension settings screen or by updating your settings.json file:

"amp.mcpServers": {
  "playwright": {
    "command": "npx",
    "args": [
      "@playwright/mcp@latest"
    ]
  }
}

Amp CLI Setup:

Add via the amp mcp add command below

amp mcp add playwright -- npx @playwright/mcp@latest
Antigravity

Add via the Antigravity settings or by updating your configuration file:

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest"
      ]
    }
  }
}
Claude Code

Use the Claude Code CLI to add the Playwright MCP server:

claude mcp add playwright npx @playwright/mcp@latest
Claude Desktop

Follow the MCP install guide, use the standard config above.

Cline

Follow the instruction in the section Configuring MCP Servers

Example: Local Setup

Add the following to your cline_mcp_settings.json file:

{
  "mcpServers": {
    "playwright": {
      "type": "stdio",
      "command": "npx",
      "timeout": 30,
      "args": [
        "-y",
        "@playwright/mcp@latest"
      ],
      "disabled": false
    }
  }
}
Codex

Use the Codex CLI to add the Playwright MCP server:

codex mcp add playwright npx "@playwright/mcp@latest"

Alternatively, create or edit the configuration file ~/.codex/config.toml and add:

[mcp_servers.playwright]
command = "npx"
args = ["@playwright/mcp@latest"]

For more information, see the Codex MCP documentation.

Copilot

Use the Copilot CLI to interactively add the Playwright MCP server:

/mcp add

Alternatively, create or edit the configuration file ~/.copilot/mcp-config.json and add:

{
  "mcpServers": {
    "playwright": {
      "type": "local",
      "command": "npx",
      "tools": [
        "*"
      ],
      "args": [
        "@playwright/mcp@latest"
      ]
    }
  }
}

For more information, see the Copilot CLI documentation.

Cursor

Click the button to install:

Install in Cursor

Or install manually:

Go to Cursor Settings -> MCP -> Add new MCP Server. Name to your liking, use command type with the command npx @playwright/mcp@latest. You can also verify config or add command like arguments via clicking Edit.

Factory

Use the Factory CLI to add the Playwright MCP server:

droid mcp add playwright "npx @playwright/mcp@latest"

Alternatively, type /mcp within Factory droid to open an interactive UI for managing MCP servers.

For more information, see the Factory MCP documentation.

Gemini CLI

Follow the MCP install guide, use the standard config above.

Goose

Click the button to install:

Install in Goose

Or install manually:

Go to Advanced settings -> Extensions -> Add custom extension. Name to your liking, use type STDIO, and set the command to npx @playwright/mcp. Click "Add Extension".

Grok

Use the Grok CLI to add the Playwright MCP server:

grok mcp add playwright -- npx @playwright/mcp@latest

Alternatively, create or edit the configuration file ~/.grok/config.toml and add:

[mcp_servers.playwright]
command = "npx"
args = ["@playwright/mcp@latest"]

For more information, see the Grok MCP documentation.

Junie

To add the Playwright MCP server in Junie CLI:

  1. Type /mcp
  2. Press Ctrl+A to add a new MCP server
  3. Select Playwright from the list

Alternatively, add to .junie/mcp/mcp.json:

{
  "mcpServers": {
    "Playwright": {
      "command": "npx",
      "args": [
        "-y",
        "@playwright/mcp@latest"
      ]
    }
  }
}

For more information, see the Junie MCP configuration documentation.

Kiro

Add to Kiro

Follow the MCP Servers documentation. For example in .kiro/settings/mcp.json:

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest"
      ]
    }
  }
}
LM Studio

Click the button to install:

Add MCP Server playwright to LM Studio

Or install manually:

Go to Program in the right sidebar -> Install -> Edit mcp.json. Use the standard config above.

opencode

Follow the MCP Servers documentation. For example in ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "playwright": {
      "type": "local",
      "command": [
        "npx",
        "@playwright/mcp@latest"
      ],
      "enabled": true
    }
  }
}

Qodo Gen

Open Qodo Gen chat panel in VSCode or IntelliJ → Connect more tools → + Add new MCP → Paste the standard config above.

Click Save.

VS Code

Click the button to install:

Install in VS Code Install in VS Code Insiders

Or install manually:

Follow the MCP install guide, use the standard config above. You can also install the Playwright MCP server using the VS Code CLI:

# For VS Code
code --add-mcp '{"name":"playwright","command":"npx","args":["@playwright/mcp@latest"]}'

After installation, the Playwright MCP server will be available for use with your GitHub Copilot agent in VS Code.

Warp

Go to Settings -> AI -> Manage MCP Servers -> + Add to add an MCP Server. Use the standard config above.

Alternatively, use the slash command /add-mcp in the Warp prompt and paste the standard config from above:

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest"
      ]
    }
  }
}
Windsurf

Follow Windsurf MCP documentation. Use the standard config above.

Configuration

Playwright MCP server supports following arguments. They can be provided in the JSON configuration above, as a part of the "args" list:

OptionDescription
--allowed-hosts <hosts...>comma-separated list of hosts this server is allowed to serve from. Defaults to the host the server is bound to. Pass '*' to disable the host check.
env PLAYWRIGHT_MCP_ALLOWED_HOSTS
--allowed-origins semicolon-separated list of TRUSTED origins to allow the browser to request. Default is to allow all. Important: does not serve as a security boundary and does not affect redirects.
env PLAYWRIGHT_MCP_ALLOWED_ORIGINS
--allow-unrestricted-file-accessallow access to files outside of the workspace roots. Also allows unrestricted access to file:// URLs. By default access to file system is restricted to workspace root directories (or cwd if no roots are configured) only, and navigation to file:// URLs is blocked.
env PLAYWRIGHT_MCP_ALLOW_UNRESTRICTED_FILE_ACCESS
--blocked-origins semicolon-separated list of origins to block the browser from requesting. Blocklist is evaluated before allowlist. If used without the allowlist, requests not matching the blocklist are still allowed. Important: does not serve as a security boundary and does not affect redirects.
env PLAYWRIGHT_MCP_BLOCKED_ORIGINS
--block-service-workersblock service workers
env PLAYWRIGHT_MCP_BLOCK_SERVICE_WORKERS
--browser browser or chrome channel to use, possible values: chrome, firefox, webkit, msedge.
env PLAYWRIGHT_MCP_BROWSER
--caps comma-separated list of additional capabilities to enable, possible values: vision, pdf, devtools.
env PLAYWRIGHT_MCP_CAPS
--cdp-endpoint CDP endpoint to connect to.
env PLAYWRIGHT_MCP_CDP_ENDPOINT
--cdp-header <headers...>CDP headers to send with the connect request, multiple can be specified.
env PLAYWRIGHT_MCP_CDP_HEADERS
--cdp-timeout timeout in milliseconds for connecting to CDP endpoint, defaults to 30000ms
env PLAYWRIGHT_MCP_CDP_TIMEOUT
--codegen specify the language to use for code generation, possible values: "typescript", "python", "java", "csharp", "none". Default is "typescript".
env PLAYWRIGHT_MCP_CODEGEN
--config path to the configuration file.
env PLAYWRIGHT_MCP_CONFIG
--console-level level of console messages to return: "error", "warning", "info", "debug". Each level includes the messages of more severe levels.
env PLAYWRIGHT_MCP_CONSOLE_LEVEL
--device device to emulate, for example: "iPhone 15"
env PLAYWRIGHT_MCP_DEVICE
--mobileemulate a generic mobile device (Pixel 10 for Chromium, iPhone 17 for WebKit). Mobile pages are usually lighter, which saves tokens. Cannot be combined with --device.
env PLAYWRIGHT_MCP_MOBILE
--executable-path path to the browser executable.
env PLAYWRIGHT_MCP_EXECUTABLE_PATH
--extensionConnect to a running browser instance (Edge/Chrome only). Requires the "Playwright Extension" to be installed.
env PLAYWRIGHT_MCP_EXTENSION
--endpoint Bound browser endpoint to connect to.
env PLAYWRIGHT_MCP_ENDPOINT
--grant-permissions <permissions...>List of permissions to grant to the browser context, for example "geolocation", "clipboard-read", "clipboard-write".
env PLAYWRIGHT_MCP_GRANT_PERMISSIONS
--headlessrun browser in headless mode, headed by default
env PLAYWRIGHT_MCP_HEADLESS
--host host to bind server to. Default is localhost. Use 0.0.0.0 to bind to all interfaces.
env PLAYWRIGHT_MCP_HOST
--ignore-https-errorsignore https errors
env PLAYWRIGHT_MCP_IGNORE_HTTPS_ERRORS
--init-page <path...>path to TypeScript file to evaluate on Playwright page object
env PLAYWRIGHT_MCP_INIT_PAGE
--init-script <path...>path to JavaScript file to add as an initialization script. The script will be evaluated in every page before any of the page's scripts. Can be specified multiple times.
env PLAYWRIGHT_MCP_INIT_SCRIPT
--isolatedkeep the browser profile in memory, do not save it to disk.
env PLAYWRIGHT_MCP_ISOLATED
--image-responses whether to send image responses to the client. Can be "allow" or "omit", Defaults to "allow".
env PLAYWRIGHT_MCP_IMAGE_RESPONSES
--no-sandboxdisable the sandbox for all process types that are normally sandboxed.
env PLAYWRIGHT_MCP_NO_SANDBOX
--output-dir path to the directory for output files.
env PLAYWRIGHT_MCP_OUTPUT_DIR
--output-max-size Threshold for evicting old output files, in bytes.
env PLAYWRIGHT_MCP_OUTPUT_MAX_SIZE
--port port to listen on for SSE transport.
env PLAYWRIGHT_MCP_PORT
--proxy-bypass comma-separated domains to bypass proxy, for example ".com,chromium.org,.domain.com"
env PLAYWRIGHT_MCP_PROXY_BYPASS
--proxy-server specify proxy server, for example "http://myproxy:3128" or "socks5://myproxy:8080"
env PLAYWRIGHT_MCP_PROXY_SERVER
--sandboxenable the sandbox for all process types that are normally not sandboxed.
env PLAYWRIGHT_MCP_SANDBOX
--save-sessionWhether to save the Playwright MCP session into the output directory.
env PLAYWRIGHT_MCP_SAVE_SESSION
--secrets path to a file containing secrets in the dotenv format
env PLAYWRIGHT_MCP_SECRETS_FILE
--shared-browser-contextreuse the same browser context between all connected HTTP clients.
env PLAYWRIGHT_MCP_SHARED_BROWSER_CONTEXT
--snapshot-boxesinclude each element's bounding box as [box=x,y,width,height] in snapshots. Coordinates are viewport-relative, in CSS pixels.
env PLAYWRIGHT_MCP_SNAPSHOT_BOXES
--snapshot-mode when taking snapshots for responses, specifies the mode to use. Can be "full" or "none". Default is "full".
env PLAYWRIGHT_MCP_SNAPSHOT_MODE
--storage-state path to the storage state file for isolated sessions.
env PLAYWRIGHT_MCP_STORAGE_STATE
--test-id-attribute specify the attribute to use for test ids, defaults to "data-testid"
env PLAYWRIGHT_MCP_TEST_ID_ATTRIBUTE
--timeout-action specify action timeout in milliseconds, defaults to 5000ms
env PLAYWRIGHT_MCP_TIMEOUT_ACTION
--timeout-navigation specify navigation timeout in milliseconds, defaults to 60000ms
env PLAYWRIGHT_MCP_TIMEOUT_NAVIGATION
--timeout-settle how long to wait after each action for triggered work to settle, in milliseconds, defaults to 500ms
env PLAYWRIGHT_MCP_TIMEOUT_SETTLE
--user-agent specify user agent string
env PLAYWRIGHT_MCP_USER_AGENT
--user-data-dir path to the user data directory. If not specified, a temporary directory will be created.
env PLAYWRIGHT_MCP_USER_DATA_DIR
--viewport-size specify browser viewport size in pixels, for example "1280x720"
env PLAYWRIGHT_MCP_VIEWPORT_SIZE

User profile

You can run Playwright MCP with persistent profile like a regular browser (default), in isolated contexts for testing sessions, or connect to your existing browser using the browser extension.

Persistent profile

All the logged in information will be stored in the persistent profile, you can delete it between sessions if you'd like to clear the offline state. Persistent profile is located at the following locations and you can override it with the --user-data-dir argument.

# Windows
%USERPROFILE%\AppData\Local\ms-playwright\mcp-{channel}-{workspace-hash}

# macOS
- ~/Library/Caches/ms-playwright/mcp-{channel}-{workspace-hash}

# Linux
- ~/.cache/ms-playwright/mcp-{channel}-{workspace-hash}

{workspace-hash} is derived from the MCP client's workspace root, so different projects get separate profiles automatically.

[!IMPORTANT] A persistent profile can only be used by one browser instance at a time, so concurrent MCP clients sharing the same workspace will conflict. To run several clients in parallel, start each additional client with --isolated or point it at a distinct --user-data-dir.

Isolated

In the isolated mode, each session is started in the isolated profile. Every time you ask MCP to close the browser, the session is closed and all the storage state for this session is lost. You can provide initial storage state to the browser via the config's contextOptions or via the --storage-state argument. Learn more about the storage state here.

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest",
        "--isolated",
        "--storage-state={path/to/storage.json}"
      ]
    }
  }
}

Browser Extension

The Playwright MCP Chrome Extension allows you to connect to existing browser tabs and leverage your logged-in sessions and browser state. See microsoft/playwright › packages/extension for installation and setup instructions.

Initial state

There are multiple ways to provide the initial state to the browser context or a page.

For the storage state, you can either:

  • Start with a user data directory using the --user-data-dir argument. This will persist all browser data between the sessions.
  • Start with a storage state file using the --storage-state argument. This will load cookies and local storage from the file into an isolated browser context.

For the page state, you can use:

  • --init-page to point to a TypeScript file that will be evaluated on the Playwright page object. This allows you to run arbitrary code to set up the page.
// init-page.ts
export default async ({ page }) => {
  await page.context().grantPermissions(['geolocation']);
  await page.context().setGeolocation({ latitude: 37.7749, longitude: -122.4194 });
  await page.setViewportSize({ width: 1280, height: 720 });
};
  • --init-script to point to a JavaScript file that will be added as an initialization script. The script will be evaluated in every page before any of the page's scripts. This is useful for overriding browser APIs or setting up the environment.
// init-script.js
window.isPlaywrightMCP = true;

Configuration file

The Playwright MCP server can be configured using a JSON configuration file. You can specify the configuration file using the --config command line option:

npx @playwright/mcp@latest --config path/to/config.json
Configuration file schema
{
  /**
   * The browser to use.
   */
  browser?: {
    /**
     * The type of browser to use.
     */
    browserName?: 'chromium' | 'firefox' | 'webkit';

    /**
     * Keep the browser profile in memory, do not save it to disk.
     */
    isolated?: boolean;

    /**
     * Path to a user data directory for browser profile persistence.
     * Temporary directory is created by default.
     */
    userDataDir?: string;

    /**
     * Launch options passed to
     * @see https://playwright.dev/docs/api/class-browsertype#browser-type-launch-persistent-context
     *
     * This is useful for settings options like `channel`, `headless`, `executablePath`, etc.
     */
    launchOptions?: playwright.LaunchOptions;

    /**
     * Context options for the browser context.
     *
     * This is useful for settings options like `viewport`.
     */
    contextOptions?: playwright.BrowserContextOptions;

    /**
     * Chrome DevTools Protocol endpoint to connect to an exi

Files in the repo

Repository payload24 top-level entries
  • .azure-pipelines
  • .claude
  • .devcontainer
  • .github
  • src
  • tests
  • .gitignore
  • .npmignore
  • CLAUDE.md
  • cli.js
  • config.d.ts
  • CONTRIBUTING.md
  • Dockerfile
  • index.d.ts
  • index.js
  • LICENSE
  • package-lock.json
  • package.json
  • playwright.config.ts
  • README.md
  • roll.js
  • SECURITY.md
  • server.json
  • update-readme.js

Discussion (0)

Ask about usage, or say what you built with it

Sign in to join the discussion.

No comments yet. Be the first to say what this is good for.

More connectors

High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in milliseconds. 158 languages, sub-ms queries, 99% fewer tokens. Single static binary, zero dependencies.

43k

Universal provider proxy for OpenAI Codex & Claude Code — use any LLM (Claude, Gemini, Grok, DeepSeek, Ollama…) with Codex CLI, App, SDK, and Claude Code

14k
okf-memory/
okf-agent-memory

Git-native persistent memory for AI coding agents. Implements Google OKF v0.2 with sub-300µs in-memory BM25 search, embedded MCP server, and progressive disclosure. Slashes token bloat by 80% with zero external databases or dependencies. Built in pure Go.

547
tirth8205/
code-review-graph

Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo workflows.

31k
2akouwu/
reverify

Stop your AI from making things up — it proposes, deterministic tools decide, every claim checked against ground truth with evidence. Grounded facts and context survive resets. Reverse engineering is the proving ground. MCP server + CLI.

1.1k
t8y2/dbxConnectors

20 MB lightweight cross-platform database client for 90+ databases, including MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, SQL Server, and Dameng. Built-in AI, MCP Server, CLI, desktop and Docker. | 轻量级跨平台数据库管理工具,支持 MySQL、PostgreSQL、SQLite、Redis、MongoDB、达梦等 90+ 数据库,提供桌面端、Docker、CLI、内置 AI 助手和 MCP Server。

19k