Playwright MCP Plus

🌐 Language / 语言: English | 中文

🎭 See the Difference!

😫 Without Playwright Plus MCP

Single Browser Limitation: Only one browser automation session at a time. Session conflicts destroy your workflow...

📹 Demo Video:

🚀 With Playwright Plus MCP

🎯 GAME CHANGER: Open Multiple Browsers Simultaneously for Concurrent Automation Testing!

Experience the power of parallel browser automation - run multiple automated tests across different projects at the same time, each with their own persistent sessions!

📹 Demo Video:

💡 Note: The videos demonstrate the revolutionary difference - from single browser limitation to unlimited concurrent browser automation.

🔥 What You Just Witnessed:

😫 Before: ONE browser only. Opening a new project = Session destroyed. Manual re-login every time.
🚀 After: UNLIMITED CONCURRENT BROWSERS! Open 5, 10, 20+ browser automation sessions simultaneously. Each project maintains its own persistent state. True parallel automation testing at scale!

Playwright MCP Plus

A enhanced Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright.

🎯 Key Innovation: Project-Level Session Isolation

⚡ The Problem We Solve:

SINGLE BROWSER BOTTLENECK: Regular Playwright MCP = only ONE browser automation session at a time
Opening multiple project windows causes catastrophic session conflicts
Each new automation task destroys the previous browser session
Automation testing becomes impossible at scale - you can't run parallel tests
Constant re-authentication kills productivity and breaks CI/CD workflows

🚀 Our Revolutionary Solution: 🎯 UNLIMITED CONCURRENT BROWSER AUTOMATION - Run multiple automated tests simultaneously across different projects, each with isolated persistent sessions!

✨ What This Unlocks for You:

🚀 CONCURRENT AUTOMATION TESTING - Run 10+ browser automation sessions simultaneously without conflicts
🔄 Never lose login states again - each project maintains its own authenticated sessions
🪟 Parallel project workflows - automate testing across multiple projects at the same time
🧪 Scalable test automation - your test suites run in parallel, faster and more reliably
💾 Sessions persist across IDE restarts - close and reopen projects, all sessions remain intact
🎯 Zero configuration required - works out-of-the-box with intelligent defaults

🚀 Enhanced Features (vs Official Playwright MCP)

This enhanced version maintains 100% backward compatibility with the official Playwright MCP while unlocking unlimited concurrent browser automation:

🎯 CONCURRENT AUTOMATION TESTING

🚀 UNLIMITED PARALLEL BROWSERS: Run multiple browser automation sessions simultaneously without conflicts
⚡ SCALABLE TEST AUTOMATION: Execute automated tests across multiple projects concurrently
🔄 ZERO SESSION INTERFERENCE: Each browser session is completely isolated from others

🔒 Project Session Isolation

🏗️ Automatic Project Detection: Each project gets its own isolated browser session
💾 Persistent Login States: Stay logged in across IDE restarts and window switches
🚪 No More Re-authentication: Your automated tests and workflows run uninterrupted
📁 Clean Project Directories: No session files cluttering your project folders (by default)
🌍 Cross-Platform Support: Intelligent storage location selection for Windows, macOS, Linux

🛠️ Multiple Storage Strategies

system: Store in OS cache directory (recommended, user-invisible)
project: Store in project directory (legacy behavior)
custom: Store in custom location

⚙️ Configuration Parameters

--project-isolation: Enable project-level session isolation (default: disabled)
--project-isolation-session-strategy: Choose storage strategy (default: "system")
--project-isolation-session-root-dir: Custom root directory for session storage

✅ Revolutionary Advantages over Official Version

🚀 UNLIMITED CONCURRENT BROWSERS: Run multiple browser automation sessions simultaneously (vs. single session limitation)
⚡ PARALLEL AUTOMATION TESTING: Execute automated tests across multiple projects at the same time
✅ 100% Backward Compatible: Drop-in replacement for official version
✅ Multi-Project Workflow: Work on multiple projects without session conflicts
✅ Persistent Authentication: Never lose login states between sessions
✅ Scalable Test Automation: Eliminates re-login overhead and enables parallel test execution
✅ Clean Workspace: No session files in project directories by default
✅ Conflict-Free: Uses official Playwright path structure to avoid conflicts
✅ Zero Maintenance: Automatic cleanup and management of session data

Key Features

🚀 CONCURRENT BROWSER AUTOMATION. Run unlimited parallel browser sessions for scalable automation testing.
🧩 CHROME EXTENSION MANAGEMENT. Install, uninstall, and manage Chrome extensions programmatically with automatic browser restart.
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.
🆕 Project-level isolation. Separate browser sessions per project with intelligent storage management.

Requirements

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

Getting started

First, install the Playwright MCP server with your client.

Standard config (100% compatible with official Playwright MCP):

{
  "mcpServers": {
    "playwright-plus": {
      "command": "npx",
      "args": [
        "-y",
        "@ai-coding-labs/playwright-mcp-plus@latest"
      ]
    }
  }
}

Enhanced config with project isolation (recommended):

{
  "mcpServers": {
    "playwright-plus": {
      "command": "npx",
      "args": [
        "-y",
        "@ai-coding-labs/playwright-mcp-plus@latest",
        "--project-isolation"
      ]
    }
  }
}

Advanced config with custom session storage:

{
  "mcpServers": {
    "playwright-plus": {
      "command": "npx",
      "args": [
        "-y",
        "@ai-coding-labs/playwright-mcp-plus@latest",
        "--project-isolation",
        "--project-isolation-session-strategy=custom",
        "--project-isolation-session-root-dir=/custom/session/path"
      ]
    }
  }
}

💡 Pro Tip for Multi-Project Workflows:

Once you enable --project-isolation, each of your projects will automatically get its own browser session. When you call any browser tool, simply include the project parameters:

// Each project gets isolated sessions automatically
browser_navigate({
  url: "https://yourapp.com",
  projectDrive: "/",                    // For macOS/Linux: "/", For Windows: "C:"
  projectPath: "/path/to/your/project"  // Absolute path to your project directory
})

This ensures your login states, cookies, and browser data never interfere between different projects!

🎬 Real-World Usage Scenario

Before (Official Playwright MCP):

# Working on Project A - login to admin panel
browser_navigate("https://myapp-staging.com/admin")
# Login with credentials, do some testing...

# Switch to Project B window - session lost! 😱
browser_navigate("https://different-app.com/dashboard") 
# All Project A login states are gone, must login again

# Switch back to Project A - login lost again! 😱
# Must re-authenticate every single time

After (With Project Isolation):

# Project A window - gets its own isolated session
browser_navigate({
  url: "https://myapp-staging.com/admin",
  projectDrive: "/",
  projectPath: "/Users/you/projects/project-a"
})
# Login once, stays logged in forever ✨

# Project B window - completely separate session  
browser_navigate({
  url: "https://different-app.com/dashboard",
  projectDrive: "/", 
  projectPath: "/Users/you/projects/project-b"
})
# Login once, independent of Project A ✨

# Switch back to Project A - STILL LOGGED IN! 🎉
# Run automated tests without re-authentication
# Perfect for CI/CD pipelines and development workflows

The Result: Your automated tests run 10x faster, your development workflow is uninterrupted, and you can work on multiple projects simultaneously without losing authentication state.

🧩 Chrome Extension Management

Playwright MCP Plus includes powerful Chrome extension management capabilities that allow you to programmatically install, uninstall, and manage Chrome extensions with automatic browser restart for immediate effect.

Key Features:

🚀 One-Click Installation: Install extensions directly from Chrome Web Store URLs or extension IDs
🔄 Automatic Browser Restart: Extensions become available immediately after installation
🗑️ Clean Uninstallation: Remove extensions completely with automatic cleanup
📋 Extension Registry: Track all installed extensions with detailed information
🏠 Local Management: Extensions are stored locally in ~/.mcp-extensions/ directory

Usage Examples:

// Install an extension by URL with immediate loading
browser_extension_install({
  extensionUrl: "https://chromewebstore.google.com/detail/json-formatter/bcjindcccaagfpapjjmafapmmgkkhgoa",
  loadImmediately: true,
  projectDrive: "/",
  projectPath: "/path/to/your/project"
})

// Install an extension by ID
browser_extension_install({
  extensionId: "chklaanhfefbnpoihckbnefhakgolnmc",
  loadImmediately: true
})

// List all installed extensions
browser_extension_list()

// Uninstall an extension with immediate effect
browser_extension_uninstall({
  extensionId: "bcjindcccaagfpapjjmafapmmgkkhgoa",
  restartImmediately: true
})

Perfect for:

🧪 Automated Testing: Install testing extensions for your test suites
🛠️ Development Workflows: Quickly set up development environments with required extensions
🔧 CI/CD Pipelines: Programmatically manage browser extensions in automated workflows
📊 Web Scraping: Install extensions that enhance data extraction capabilities

Claude Code

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

Standard version:

claude mcp add playwright-plus npx -y @ai-coding-labs/playwright-mcp-plus@latest

With project isolation (recommended):

claude mcp add playwright-plus npx -y @ai-coding-labs/playwright-mcp-plus@latest --project-isolation

Claude Desktop

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

Cursor

Click the button to install:

Or install manually:

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

Gemini CLI

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

Goose

Click the button to install:

Or install manually:

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

LM Studio

Click the button to install:

Or install manually:

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

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:

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-plus","command":"npx","args":["-y","@ai-coding-labs/playwright-mcp-plus@latest","--project-isolation"]}'

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

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:

> npx @playwright/mcp@latest --help
  --allowed-origins <origins>                      semicolon-separated list of origins to allow the browser to request. Default is to allow all.
  --blocked-origins <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.
  --block-service-workers                          block service workers
  --browser <browser>                              browser or chrome channel to use, possible values: chrome, firefox, webkit, msedge.
  --caps <caps>                                    comma-separated list of additional capabilities to enable, possible values: vision, pdf.
  --cdp-endpoint <endpoint>                        CDP endpoint to connect to.
  --config <path>                                  path to the configuration file.
  --device <device>                                device to emulate, for example: "iPhone 15"
  --executable-path <path>                         path to the browser executable.
  --headless                                       run browser in headless mode, headed by default
  --host <host>                                    host to bind server to. Default is localhost. Use 0.0.0.0 to bind to all interfaces.
  --ignore-https-errors                            ignore https errors
  --isolated                                       keep the browser profile in memory, do not save it to disk.
  --image-responses <mode>                         whether to send image responses to the client. Can be "allow" or "omit", Defaults to "allow".
  --no-sandbox                                     disable the sandbox for all process types that are normally sandboxed.
  --output-dir <path>                              path to the directory for output files.
  --port <port>                                    port to listen on for SSE transport.
  --project-isolation                              enable project-level session isolation using project path from MCP context.
  --project-isolation-session-strategy <strategy>  session directory strategy for project isolation: system, project, custom. Defaults to "system". (default: "system")
  --project-isolation-session-root-dir <path>      custom root directory for session storage when using project isolation (only used with --project-isolation-session-strategy=custom).
  --proxy-bypass <bypass>                          comma-separated domains to bypass proxy, for example ".com,chromium.org,.domain.com"
  --proxy-server <proxy>                           specify proxy server, for example "http://myproxy:3128" or "socks5://myproxy:8080"
  --save-session                                   Whether to save the Playwright MCP session into the output directory.
  --save-trace                                     Whether to save the Playwright Trace of the session into the output directory.
  --storage-state <path>                           path to the storage state file for isolated sessions.
  --user-agent <ua string>                         specify user agent string
  --user-data-dir <path>                           path to the user data directory. If not specified, a temporary directory will be created.
  --viewport-size <size>                           specify browser viewport size in pixels, for example "1280, 720"

User profile

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

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}-profile

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

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

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-plus": {
      "command": "npx",
      "args": [
        "@ai-coding-labs/playwright-mcp-plus@latest",
        "--isolated",
        "--storage-state={path/to/storage.json}"
      ]
    }
  }
}

🔒 Project Isolation (Enhanced Feature)

Project Isolation allows each project to maintain its own separate browser session with independent login states, cookies, and localStorage. This prevents cross-project interference while keeping your workspace clean.

Default Behavior (Backward Compatible)

Without any isolation flags, sessions are shared between all projects (identical to official Playwright MCP):

{
  "mcpServers": {
    "playwright-plus": {
      "command": "npx",
      "args": ["@ai-coding-labs/playwright-mcp-plus@latest"]
    }
  }
}

Recommended: System Strategy (Zero Config)

Enable project isolation with sessions stored in OS cache directory (invisible to users):

{
  "mcpServers": {
    "playwright-plus": {
      "command": "npx",
      "args": [
        "@ai-coding-labs/playwright-mcp-plus@latest",
        "--project-isolation"
      ]
    }
  }
}

Storage locations by OS:

Windows: %LOCALAPPDATA%/ms-playwright/mcp-chrome-profile/playwright-plus-mcp/project-hash/
macOS: ~/Library/Caches/ms-playwright/mcp-chrome-profile/playwright-plus-mcp/project-hash/
Linux: ~/.cache/ms-playwright/mcp-chrome-profile/playwright-plus-mcp/project-hash/

Project Strategy

Store sessions in project directory (creates .user-session-data-directory/):

{
  "mcpServers": {
    "playwright-plus": {
      "command": "npx",
      "args": [
        "@ai-coding-labs/playwright-mcp-plus@latest",
        "--project-isolation",
        "--project-isolation-session-strategy=project"
      ]
    }
  }
}

Custom Strategy

Store sessions in a custom location:

{
  "mcpServers": {
    "playwright-plus": {
      "command": "npx",
      "args": [
        "@ai-coding-labs/playwright-mcp-plus@latest",
        "--project-isolation",
        "--project-isolation-session-strategy=custom",
        "--project-isolation-session-root-dir=/custom/sessions"
      ]
    }
  }
}

Strategy Comparison

Configuration	Session Location	Project Directory	User Visibility	Use Case
No isolation (default)	Shared cache	Clean	Hidden	Backward compatibility
System (isolation default)	OS cache directory	Clean	Hidden	Best user experience
Project	`.user-session-data-directory/`	Has session files	Visible	Legacy/debugging
Custom	Custom path	Clean	Hidden	Advanced setups

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 @ai-coding-labs/playwright-mcp-plus@latest --config path/to/config.json

Configuration file schema

{
  // Browser configuration
  browser?: {
    // Browser type to use (chromium, firefox, or webkit)
    browserName?: 'chromium' | 'firefox' | 'webkit';

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

    // Path to user data directory for browser profile persistence
    userDataDir?: string;

    // Browser launch options (see Playwright docs)
    // @see https://playwright.dev/docs/api/class-browsertype#browser-type-launch
    launchOptions?: {
      channel?: string;        // Browser channel (e.g. 'chrome')
      headless?: boolean;      // Run in headless mode
      executablePath?: string; // Path to browser executable
      // ... other Playwright launch options
    };

    // Browser context options
    // @see https://playwright.dev/docs/api/class-browser#browser-new-context
    contextOptions?: {
      viewport?: { width: number, height: number };
      // ... other Playwright context options
    };

    // CDP endpoint for connecting to existing browser
    cdpEndpoint?: string;

    // Remote Playwright server endpoint
    remoteEndpoint?: string;
  },

  // Server configuration
  server?: {
    port?: number;  // Port to listen on
    host?: string;  // Host to bind to (default: localhost)
  },

  // List of additional capabilities
  capabilities?: Array<
    'tabs' |    // Tab management
    'install' | // Browser installation
    'pdf' |     // PDF generation
    'vision' |  // Coordinate-based interactions
  >;

  // Directory for output files
  outputDir?: string;

  // Network configuration
  network?: {
    // List of origins to allow the browser to request. Default is to allow all. Origins matching both `allowedOrigins` and `blockedOrigins` will be blocked.
    allowedOrigins?: string[];

    // List of origins to block the browser to request. Origins matching both `allowedOrigins` and `blockedOrigins` will be blocked.
    blockedOrigins?: string[];
  };
 
  /**
   * Whether to send image responses to the client. Can be "allow" or "omit". 
   * Defaults to "allow".
   */
  imageResponses?: 'allow' | 'omit';

  /**
   * Enable project-level session isolation using project path from MCP context.
   * When enabled, each project gets its own isolated browser session.
   * Defaults to false (shared sessions, compatible with official Playwright MCP).
   */
  projectIsolation?: boolean;

  /**
   * Session directory storage strategy for project isolation.
   * Only used when projectIsolation is enabled.
   * - 'system': Store in OS cache directory (recommended, user-invisible)
   * - 'project': Store in project directory (legacy behavior)
   * - 'custom': Store in custom location specified by projectIsolationSessionRootDir
   * Defaults to "system".
   */
  projectIsolationSessionStrategy?: 'system' | 'project' | 'custom';

  /**
   * Custom root directory for session storage when using project isolation.
   * Only used when projectIsolationSessionStrategy is 'custom'.
   * Example: "/custom/session/storage/path"
   */
  projectIsolationSessionRootDir?: string;
}

Standalone MCP server

When running headed browser on system w/o display or from worker processes of the IDEs, run the MCP server from environment with the DISPLAY and pass the --port flag to enable HTTP transport.

npx @ai-coding-labs/playwright-mcp-plus@latest --port 8931

And then in MCP client config, set the url to the HTTP endpoint:

{
  "mcpServers": {
    "playwright-plus": {
      "url": "http://localhost:8931/mcp"
    }
  }
}

Docker

NOTE: The Docker implementation only supports headless chromium at the moment.

{
  "mcpServers": {
    "playwright-plus": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "--init", "--pull=always", "mcr.microsoft.com/playwright/mcp"]
    }
  }
}

You can build the Docker image yourself.

docker build -t mcr.microsoft.com/playwright/mcp .

Programmatic usage

import http from 'http';

import { createConnection } from '@ai-coding-labs/playwright-mcp-plus';
import { SSEServerTransport } from '@modelcontextprotocol/sdk/server/sse.js';

http.createServer(async (req, res) => {
  // ...

  // Creates a headless Playwright MCP server with SSE transport
  const connection = await createConnection({ browser: { launchOptions: { headless: true } } });
  const transport = new SSEServerTransport('/messages', res);
  await connection.sever.connect(transport);

  // ...
});

Tools

Core automation

browser_click
- Title: Click
- Description: Perform click on a web page
- Parameters:
  - element (string): Human-readable element description used to obtain permission to interact with the element
  - ref (string): Exact target element reference from the page snapshot
  - doubleClick (boolean, optional): Whether to perform a double click instead of a single click
  - button (string, optional): Button to click, defaults to left
- Read-only: false

browser_close
- Title: Close browser
- Description: Close the page
- Parameters:
  - projectDrive (string, optional): Project drive letter or root (e.g., "C:", "/") for session isolation
  - projectPath (string, optional): Absolute path to project root directory for session isolation
- Read-only: true

browser_console_messages
- Title: Get console messages
- Description: Returns all console messages
- Parameters: None
- Read-only: true

browser_drag
- Title: Drag mouse
- Description: Perform drag and drop between two elements
- Parameters:
  - startElement (string): Human-readable source element description used to obtain the permission to interact with the element
  - startRef (string): Exact source element reference from the page snapshot
  - endElement (string): Human-readable target element description used to obtain the permission to interact with the element
  - endRef (string): Exact target element reference from the page snapshot
- Read-only: false

browser_evaluate
- Title: Evaluate JavaScript
- Description: Evaluate JavaScript expression on page or element
- Parameters:
  - function (string): () => { /* code / } or (element) => { / code */ } when element is provided
  - element (string, optional): Human-readable element description used to obtain permission to interact with the element
  - ref (string, optional): Exact target element reference from the page snapshot
- Read-only: false

browser_extension_install
- Title: Install Chrome Extension
- Description: Install a Chrome extension from the Chrome Web Store by downloading and managing it locally
- Parameters:
  - extensionId (string, optional): Chrome extension ID (e.g., "cjpalhdlnbpafiamejdnhcphjbkeiagm")
  - extensionUrl (string, optional): Full Chrome Web Store URL of the extension
  - waitForInstall (boolean, optional): Whether to wait for installation to complete
  - loadImmediately (boolean, optional): Whether to restart browser to load the extension immediately
  - projectDrive (string, optional): Project drive letter or root (e.g., "C:", "/") for session isolation
  - projectPath (string, optional): Absolute path to project root directory for session isolation
- Read-only: false

browser_extension_list
- Title: List Installed Extensions
- Description: List all MCP-managed Chrome extensions
- Parameters:
  - projectDrive (string, optional): Project drive letter or root (e.g., "C:", "/") for session isolation
  - projectPath (string, optional): Absolute path to project root directory for session isolation
- Read-only: true

browser_extension_uninstall
- Title: Uninstall Chrome Extension
- Description: Uninstall a Chrome extension from MCP management and restart browser
- Parameters:
  - extensionId (string): Chrome extension ID to uninstall (e.g., "bcjindcccaagfpapjjmafapmmgkkhgoa")
  - restartImmediately (boolean, optional): Whether to restart browser immediately after uninstalling
  - projectDrive (string, optional): Project drive letter or root (e.g., "C:", "/") for session isolation
  - projectPath (string, optional): Absolute path to project root directory for session isolation
- Read-only: false

browser_file_upload
- Title: Upload files
- Description: Upload one or multiple files
- Parameters:
  - paths (array): The absolute paths to the files to upload. Can be a single file or multiple files.
- Read-only: false

browser_handle_dialog
- Title: Handle a dialog
- Description: Handle a dialog
- Parameters:
  - accept (boolean): Whether to accept the dialog.
  - promptText (string, optional): The text of the prompt in case of a prompt dialog.
- Read-only: false

browser_hover
- Title: Hover mouse
- Description: Hover over element on page
- Parameters:
  - element (string): Human-readable element description used to obtain permission to interact with the element
  - ref (string): Exact target element reference from the page snapshot
- Read-only: true

browser_navigate
- Title: Navigate to a URL
- Description: Navigate to a URL
- Parameters:
  - url (string): The URL to navigate to
  - projectDrive (string, optional): Project drive letter or root (e.g., "C:", "/") for session isolation
  - projectPath (string, optional): Absolute path to project root directory for session isolation
- Read-only: false

browser_navigate_back
- Title: Go back
- Description: Go back to the previous page
- Parameters: None
- Read-only: true

browser_navigate_forward
- Title: Go forward
- Description: Go forward to the next page
- Parameters: None
- Read-only: true

browser_network_requests
- Title: List network requests
- Description: Returns all network requests since loading the page
- Parameters: None
- Read-only: true

browser_press_key
- Title: Press a key
- Description: Press a key on the keyboard
- Parameters:
  - key (string): Name of the key to press or a character to generate, such as ArrowLeft or a
- Read-only: false

browser_resize
- Title: Resize browser window
- Description: Resize the browser window
- Parameters:
  - width (number): Width of the browser window
  - height (number): Height of the browser window
- Read-only: true

browser_select_option
- Title: Select option
- Description: Select an option in a dropdown
- Parameters:
  - element (string): Human-readable element description used to obtain permission to interact with the element
  - ref (string): Exact target element reference from the page snapshot
  - values (array): Array of values to select in the dropdown. This can be a single value or multiple values.
- Read-only: false

browser_snapshot
- Title: Page snapshot
- Description: Capture accessibility snapshot of the current page, this is better than screenshot
- Parameters:
  - projectDrive (string, optional): Project drive letter or root (e.g., "C:", "/") for session isolation
  - projectPath (string, optional): Absolute path to project root directory for session isolation
- Read-only: true

browser_take_screenshot
- Title: Take a screenshot
- Description: Take a screenshot of the current page. You can't perform actions based on the screenshot, use browser_snapshot for actions.
- Parameters:
  - type (string, optional): Image format for the screenshot. Default is png.
  - filename (string, optional): File name to save the screenshot to. Defaults to page-{timestamp}.{png|jpeg} if not specified.
  - element (string, optional): Human-readable element description used to obtain permission to screenshot the element. If not provided, the screenshot will be taken of viewport. If element is provided, ref must be provided too.
  - ref (string, optional): Exact target element reference from the page snapshot. If not provided, the screenshot will be taken of viewport. If ref is provided, element must be provided too.
  - fullPage (boolean, optional): When true, takes a screenshot of the full scrollable page, instead of the currently visible viewport. Cannot be used with element screenshots.
- Read-only: true

browser_type
- Title: Type text
- Description: Type text into editable element
- Parameters:
  - element (string): Human-readable element description used to obtain permission to interact with the element
  - ref (string): Exact target element reference from the page snapshot
  - text (string): Text to type into the element
  - submit (boolean, optional): Whether to submit entered text (press Enter after)
  - slowly (boolean, optional): Whether to type one character at a time. Useful for triggering key handlers in the page. By default entire text is filled in at once.
- Read-only: false

browser_wait_for
- Title: Wait for
- Description: Wait for text to appear or disappear or a specified time to pass
- Parameters:
  - time (number, optional): The time to wait in seconds
  - text (string, optional): The text to wait for
  - textGone (string, optional): The text to wait for to disappear
  - projectDrive (string, optional): Project drive letter or root (e.g., "C:", "/") for session isolation
  - projectPath (string, optional): Absolute path to project root directory for session isolation
- Read-only: true

Tab management

browser_tab_close
- Title: Close a tab
- Description: Close a tab
- Parameters:
  - index (number, optional): The index of the tab to close. Closes current tab if not provided.
- Read-only: false

browser_tab_list
- Title: List tabs
- Description: List browser tabs
- Parameters:
  - projectDrive (string, optional): Project drive letter or root (e.g., "C:", "/") for session isolation
  - projectPath (string, optional): Absolute path to project root directory for session isolation
- Read-only: true

browser_tab_new
- Title: Open a new tab
- Description: Open a new tab
- Parameters:
  - url (string, optional): The URL to navigate to in the new tab. If not provided, the new tab will be blank.
  - projectDrive (string, optional): Project drive letter or root (e.g., "C:", "/") for session isolation
  - projectPath (string, optional): Absolute path to project root directory for session isolation
- Read-only: true

browser_tab_select
- Title: Select a tab
- Description: Select a tab by index
- Parameters:
  - index (number): The index of the tab to select
- Read-only: true

Browser installation

browser_install
- Title: Install the browser specified in the config
- Description: Install the browser specified in the config. Call this if you get an error about the browser not being installed.
- Parameters:
  - projectDrive (string, optional): Project drive letter or root (e.g., "C:", "/") for session isolation
  - projectPath (string, optional): Absolute path to project root directory for session isolation
- Read-only: false

Coordinate-based (opt-in via --caps=vision)

browser_mouse_click_xy
- Title: Click
- Description: Click left mouse button at a given position
- Parameters:
  - element (string): Human-readable element description used to obtain permission to interact with the element
  - x (number): X coordinate
  - y (number): Y coordinate
- Read-only: false

browser_mouse_drag_xy
- Title: Drag mouse
- Description: Drag left mouse button to a given position
- Parameters:
  - element (string): Human-readable element description used to obtain permission to interact with the element
  - startX (number): Start X coordinate
  - startY (number): Start Y coordinate
  - endX (number): End X coordinate
  - endY (number): End Y coordinate
- Read-only: false

browser_mouse_move_xy
- Title: Move mouse
- Description: Move mouse to a given position
- Parameters:
  - element (string): Human-readable element description used to obtain permission to interact with the element
  - x (number): X coordinate
  - y (number): Y coordinate
- Read-only: true

PDF generation (opt-in via --caps=pdf)

browser_pdf_save
- Title: Save as PDF
- Description: Save page as PDF
- Parameters:
  - filename (string, optional): File name to save the pdf to. Defaults to page-{timestamp}.pdf if not specified.
- Read-only: true

Name		Name	Last commit message	Last commit date
Latest commit History 307 Commits
.github/workflows		.github/workflows
docs		docs
examples		examples
extension		extension
src		src
tests		tests
utils		utils
.gitignore		.gitignore
.npmignore		.npmignore
CHANGELOG.md		CHANGELOG.md
Dockerfile		Dockerfile
LICENSE		LICENSE
README.md		README.md
README.zh.md		README.zh.md
SECURITY.md		SECURITY.md
cli.js		cli.js
config.d.ts		config.d.ts
eslint.config.mjs		eslint.config.mjs
index.d.ts		index.d.ts
index.js		index.js
package-lock.json		package-lock.json
package.json		package.json
playwright-mcp-config.json		playwright-mcp-config.json
playwright.config.ts		playwright.config.ts
tsconfig.all.json		tsconfig.all.json
tsconfig.json		tsconfig.json

License

vibe-coding-labs/playwright-plus-mcp

Folders and files

Latest commit

History

Repository files navigation

Playwright MCP Plus

🎭 See the Difference!

😫 Without Playwright Plus MCP

🚀 With Playwright Plus MCP

Playwright MCP Plus

🎯 Key Innovation: Project-Level Session Isolation

🚀 Enhanced Features (vs Official Playwright MCP)

🎯 CONCURRENT AUTOMATION TESTING

🔒 Project Session Isolation

🛠️ Multiple Storage Strategies

⚙️ Configuration Parameters

✅ Revolutionary Advantages over Official Version

Key Features

Requirements

Getting started

🎬 Real-World Usage Scenario

🧩 Chrome Extension Management

Click the button to install:

Or install manually:

Click the button to install:

Or install manually:

Click the button to install:

Or install manually:

Click the button to install:

Or install manually:

Configuration

User profile

🔒 Project Isolation (Enhanced Feature)

Default Behavior (Backward Compatible)

Recommended: System Strategy (Zero Config)

Project Strategy

Custom Strategy

Strategy Comparison

Configuration file

Standalone MCP server

Tools

About

Resources

License

Security policy

Uh oh!

Stars

Watchers

Forks

Releases 1

Packages 0

Languages

Packages