对于 Vs Code

什么是 Playwright MCP？

Playwright MCP（微软云平台）是微软开发的一个先进框架，使开发人员能够在各种浏览器和平台上自动化Web应用程序。它旨在促进端到端测试，确保应用程序在实际场景中表现一致且可靠。Playwright MCP支持多种编程语言，使其对广泛的开发人员可用。

Playwright MCP 的特点

• 跨浏览器测试：Playwright MCP允许用户在不同浏览器（如Chrome、Firefox和Safari）上测试应用程序，确保兼容性和性能。
• 无头模式：该框架支持无头测试，允许测试在没有图形用户界面的情况下运行，从而加快测试过程。
• 自动等待：Playwright MCP会自动等待元素准备好再执行操作，减少测试中的不稳定性。
• 多上下文：用户可以在单个实例中创建多个浏览器上下文，支持并行测试，提高效率。
• 丰富的API：该框架提供了一套丰富的API用于与Web元素交互，使编写和维护测试变得更容易。
• 网络拦截：Playwright MCP允许开发人员拦截和修改网络请求，支持测试各种场景，包括错误处理和性能。

如何开始使用 Playwright MCP

1. 安装：要开始使用Playwright MCP，可以通过以下命令使用npm进行安装：

   npm install @playwright/mcp
   

2. 设置项目：创建一个新的JavaScript或TypeScript文件并导入Playwright MCP：

   const { chromium } = require('@playwright/mcp');
   

3. 编写第一个测试：以下是如何启动浏览器并导航到网页的简单示例：

   (async () => {
       const browser = await chromium.launch();
       const page = await browser.newPage();
       await page.goto('https://example.com');
       await browser.close();
   })();
   

4. 运行测试：可以使用Node.js运行测试：

   node your-test-file.js
   

5. 探索高级功能：通过查阅文档和尝试网络拦截和并行测试等功能，深入了解Playwright MCP的能力。

常见问题解答

Playwright MCP支持哪些编程语言？

Playwright MCP支持多种编程语言，包括JavaScript、TypeScript、Python、C#和Java，使其对不同背景的开发人员具有多样性。

Playwright MCP是免费使用的吗？

是的，Playwright MCP是开源的，并在Apache-2.0许可证下免费使用，允许开发人员根据需要贡献和修改该框架。

我可以在CI/CD管道中运行Playwright MCP测试吗？

当然可以！Playwright MCP旨在与CI/CD管道无缝集成，允许在开发工作流程中进行自动化测试。

Playwright MCP与其他测试框架相比如何？

Playwright MCP提供了独特的功能，如自动等待、跨浏览器支持和处理多个上下文的能力，这可以提供比其他框架（如Selenium）更强大的测试体验。

我在哪里可以找到更多资源和文档？

您可以在其官方npm页面和Playwright GitHub存储库上找到Playwright MCP的全面文档和资源。

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.

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 or any other MCP client

<!-- // Generate using: node utils/generate-links.js -->

Getting started

First, install the Playwright MCP server with your client. A typical configuration looks like this:

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

<img src="https://img.shields.io/badge/VS_Code-VS_Code?style=flat-square&label=Install%20Server&color=0098FF" alt="Install in VS Code"> <img alt="Install in VS Code Insiders" src="https://img.shields.io/badge/VS_Code_Insiders-VS_Code_Insiders?style=flat-square&label=Install%20Server&color=24bfa5">

<details><summary><b>Install in VS Code</b></summary>

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.

</details> <details> <summary><b>Install in Cursor</b></summary>

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 @playwright/mcp. You can also verify config or add command like arguments via clicking Edit.

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

</details> <details> <summary><b>Install in Windsurf</b></summary>

Follow Windsurf MCP documentation. Use following configuration:

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

</details> <details> <summary><b>Install in Claude Desktop</b></summary>

Follow the MCP install guide, use following configuration:

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

</details> <details> <summary><b>Install in Claude Code</b></summary>

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

claude mcp add playwright npx @playwright/mcp@latest

</details> <details> <summary><b>Install in Qodo Gen</b></summary>

Open Qodo Gen chat panel in VSCode or IntelliJ → Connect more tools → + Add new MCP → Paste the following configuration:

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

Click <code>Save</code>.

</details>

Configuration

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

<! Options generated by update-readme.js -->

> 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.
  --browser-agent <endpoint>   Use browser agent (experimental).
  --caps <caps>                comma-separated list of capabilities to enable,
                               possible values: tabs, pdf, history, wait, files,
                               install. Default is all.
  --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", "omit", or "auto". Defaults to
                               "auto", which sends images if the client can
                               display them.
  --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.
  --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-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"
  --vision                     Run server that uses screenshots (Aria snapshots
                               are used by default)

<! End of options generated section -->

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

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

<details> <summary>Configuration file schema</summary>

{
  // 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 enabled capabilities
  capabilities?: Array<
    'core' |    // Core browser automation
    'tabs' |    // Tab management
    'pdf' |     // PDF generation
    'history' | // Browser history
    'wait' |    // Wait utilities
    'files' |   // File handling
    'install' | // Browser installation
    'testing'   // Testing
  >;

  // Enable vision mode (screenshots instead of accessibility snapshots)
  vision?: boolean;

  // 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[];
  };
 
  /**
   * Do not send image responses to the client.
   */
  noImageResponses?: boolean;
}

</details>

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 SSE transport.

npx @playwright/mcp@latest --port 8931

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

{
  "mcpServers": {
    "playwright": {
      "url": "http://localhost:8931/sse"
    }
  }
}

<details> <summary><b>Docker</b></summary>

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

{
  "mcpServers": {
    "playwright": {
      "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 .

</details> <details> <summary><b>Programmatic usage</b></summary>

import http from 'http';

import { createConnection } from '@playwright/mcp';
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);

  // ...
});

</details>

Tools

The tools are available in two modes:

1. Snapshot Mode (default): Uses accessibility snapshots for better performance and reliability
2. Vision Mode: Uses screenshots for visual-based interactions

To use Vision Mode, add the --vision flag when starting the server:

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

Vision Mode works best with the computer use models that are able to interact with elements using X Y coordinate space, based on the provided screenshot.

<! Tools generated by update-readme.js -->

<details> <summary><b>Interactions</b></summary> <!-- NOTE: This has been generated via update-readme.js -->

• browser_snapshot
  • Title: Page snapshot
  • Description: Capture accessibility snapshot of the current page, this is better than screenshot
  • Parameters: None
  • Read-only: true

<!-- NOTE: This has been generated via update-readme.js -->

• 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
  • Read-only: false

<!-- NOTE: This has been generated via update-readme.js -->

• 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

<!-- NOTE: This has been generated via update-readme.js -->

• 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

<!-- NOTE: This has been generated via update-readme.js -->

• 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

<!-- NOTE: This has been generated via update-readme.js -->

• 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

<!-- NOTE: This has been generated via update-readme.js -->

• 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

<!-- NOTE: This has been generated via update-readme.js -->

• 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
  • Read-only: true

<!-- NOTE: This has been generated via update-readme.js -->

• 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

<!-- NOTE: This has been generated via update-readme.js -->

• 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

</details> <details> <summary><b>Navigation</b></summary> <!-- NOTE: This has been generated via update-readme.js -->

• browser_navigate
  • Title: Navigate to a URL
  • Description: Navigate to a URL
  • Parameters:
    • url (string): The URL to navigate to
  • Read-only: false

<!-- NOTE: This has been generated via update-readme.js -->

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

<!-- NOTE: This has been generated via update-readme.js -->

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

</details> <details> <summary><b>Resources</b></summary> <!-- NOTE: This has been generated via update-readme.js -->

• 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:
    • raw (boolean, optional): Whether to return without compression (in PNG format). Default is false, which returns a JPEG image.
    • 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.
  • Read-only: true

<!-- NOTE: This has been generated via update-readme.js -->

• 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

<!-- NOTE: This has been generated via update-readme.js -->

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

<!-- NOTE: This has been generated via update-readme.js -->

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

</details> <details> <summary><b>Utilities</b></summary> <!-- NOTE: This has been generated via update-readme.js -->

• 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: None
  • Read-only: false

<!-- NOTE: This has been generated via update-readme.js -->

• browser_close
  • Title: Close browser
  • Description: Close the page
  • Parameters: None
  • Read-only: true

<!-- NOTE: This has been generated via update-readme.js -->

• 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

</details> <details> <summary><b>Tabs</b></summary> <!-- NOTE: This has been generated via update-readme.js -->

• browser_tab_list
  • Title: List tabs
  • Description: List browser tabs
  • Parameters: None
  • Read-only: true

<!-- NOTE: This has been generated via update-readme.js -->

• 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.
  • Read-only: true

<!-- NOTE: This has been generated via update-readme.js -->

• 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

<!-- NOTE: This has been generated via update-readme.js -->

• 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

</details> <details> <summary><b>Testing</b></summary> <!-- NOTE: This has been generated via update-readme.js -->

• browser_generate_playwright_test
  • Title: Generate a Playwright test
  • Description: Generate a Playwright test for given scenario
  • Parameters:
    • name (string): The name of the test
    • description (string): The description of the test
    • steps (array): The steps of the test
  • Read-only: true

</details> <details> <summary><b>Vision mode</b></summary> <!-- NOTE: This has been generated via update-readme.js -->

• browser_screen_capture
  • Title: Take a screenshot
  • Description: Take a screenshot of the current page
  • Parameters: None
  • Read-only: true

<!-- NOTE: This has been generated via update-readme.js -->

• browser_screen_move_mouse
  • 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

<!-- NOTE: This has been generated via update-readme.js -->

• browser_screen_click
  • Title: Click
  • Description: Click left mouse button
  • 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

<!-- NOTE: This has been generated via update-readme.js -->

• browser_screen_drag
  • Title: Drag mouse
  • Description: Drag left mouse button
  • 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

<!-- NOTE: This has been generated via update-readme.js -->

• browser_screen_type
  • Title: Type text
  • Description: Type text
  • Parameters:
    • text (string): Text to type into the element
    • submit (boolean, optional): Whether to submit entered text (press Enter after)
  • Read-only: false

<!-- NOTE: This has been generated via update-readme.js -->

• 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

<!-- NOTE: This has been generated via update-readme.js -->

• 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
  • Read-only: true

<!-- NOTE: This has been generated via update-readme.js -->

• 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

<!-- NOTE: This has been generated via update-readme.js -->

• 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

</details>

<! End of tools generated section -->