Ms Playwright MCP

Playwright MCP Guide

Rules and usage for Microsoft Playwright MCP server.

MUST-NOT-FORGET

• Use accessibility tree (not screenshots) for element selection
• Reference elements via aria-ref=e5 format from browser_snapshot
• Always call browser_snapshot before clicking to get current element refs
• Use browser_close when done to free resources
• For logged-in sessions: Use persistent user profile or storage state file

MCP Server

Repository: https://github.com/microsoft/playwright-mcp Package: @playwright/mcp

Configuration

Basic configuration (isolated session):

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

Persistent user profile (remembers logins):

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest",
        "--user-data-dir", "[USER_PROFILE_PATH]/.ms-playwright-mcp-profile"
      ]
    }
  }
}

Headless mode:

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

With timeout configuration (recommended for slow pages):

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest",
        "--timeout-action", "10000",
        "--timeout-navigation", "120000"
      ]
    }
  }
}

Reduced token usage (skip accessibility details):

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

Available Tools

Navigation

browser_navigate - Go to URL

browser_navigate(url: "https://example.com")

Element Interaction

browser_snapshot - Get accessibility tree with element refs

browser_snapshot()
// Returns tree with refs like: link "Home" [ref=e5]

browser_click - Click element by ref

browser_click(element: "Submit button", ref: "e12")
// Options: modifiers (Control, Shift, Alt), doubleClick

browser_type - Type text (clears existing, use for inputs)

browser_type(element: "Search input", ref: "e8", text: "search query")

browser_fill - Fill form field

browser_fill(element: "Email", ref: "e3", value: "user@example.com")

browser_select - Select dropdown option

browser_select(element: "Country", ref: "e15", values: ["USA"])

Advanced Interactions

browser_drag - Drag and drop

browser_drag(
  startElement: "Draggable item", startRef: "e10",
  endElement: "Drop zone", endRef: "e20"
)

browser_hover - Hover over element

browser_hover(element: "Menu", ref: "e5")

browser_press_key - Press keyboard key

browser_press_key(key: "Enter")
browser_press_key(key: "Control+A")

Inspection

browser_screenshot - Capture page screenshot

browser_screenshot()
// Options: raw (base64 instead of file)

browser_console_messages - Get console logs

browser_console_messages()
// Options: level (error, warning, info)

browser_evaluate - Execute JavaScript

browser_evaluate(expression: "document.title")

Session Management

browser_close - Close browser and free resources

browser_close()

Common Workflows

1. Navigate and Click

1. browser_navigate(url: "https://example.com")
2. browser_snapshot()  // Get current element refs
3. browser_click(element: "Login button", ref: "e12")

2. Fill Form and Submit

1. browser_snapshot()
2. browser_fill(element: "Username", ref: "e3", value: "user@example.com")
3. browser_fill(element: "Password", ref: "e5", value: "password123")
4. browser_click(element: "Submit", ref: "e8")

3. Wait for Content

After navigation or click, call browser_snapshot() again to:

• Verify page loaded correctly
• Get updated element refs
• Check for expected content

4. Extract Data

1. browser_snapshot()  // Get page content
2. browser_evaluate(expression: "document.querySelector('.price').textContent")

Element Selection Best Practices

Using Refs from Snapshot

1. Call browser_snapshot() to get current page structure
2. Find element in returned accessibility tree
3. Use the ref value (e.g., e5) in subsequent commands

Example snapshot output:

- banner [ref=e3]:
    - link "Home" [ref=e5] [cursor=pointer]:
        - /url: /
    - navigation [ref=e12]:
        - link "Docs" [ref=e13] [cursor=pointer]

Selector Priority

When refs are not available, use stable selectors:

1. [data-testid="submit"] - Best, explicit test attribute
2. getByRole('button', { name: 'Save' }) - Semantic, accessible
3. getByText('Sign in') - User-facing text
4. input[name="email"] - HTML attributes
5. Avoid: .btn-primary, #submit - Classes/IDs change frequently

Authentication Strategies

Strategy 1: Persistent User Profile

Configure --user-data-dir to persist cookies and login state:

{
  "args": [
    "@playwright/mcp@latest",
    "--user-data-dir", "[USER_PROFILE_PATH]/.ms-playwright-mcp-profile"
  ]
}

Strategy 2: Storage State File

Save authentication state to file:

// After login, save state
await context.storageState({ path: 'auth.json' });

Use with --storage-state:

{
  "args": ["@playwright/mcp@latest", "--storage-state", "auth.json"]
}

Strategy 3: Browser Extension Mode

Connect to existing browser with remote debugging:

{
  "args": ["@playwright/mcp@latest", "--extension"]
}

Start Chrome with debugging enabled:

& "[PROGRAM_FILES]\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222

Note: Known issue (GitHub #921) - may launch new Chrome instead of connecting.

Troubleshooting

npx not found

Use full path to npx:

{
  "command": "[NPX_FULL_PATH]"
}

Profile lock errors

Reset profile lock:

Remove-Item "[USER_PROFILE_PATH]\.ms-playwright-mcp-profile\SingletonLock" -Force -ErrorAction SilentlyContinue

Extension mode not connecting

Known issue (GitHub #921): --extension flag may launch new Chrome. Workaround: Ensure Chrome is running with --remote-debugging-port=9222 before starting MCP.

Element not found

1. Call browser_snapshot(mode: "tree") to refresh refs
2. Wait for page to fully load
3. Check if element is in iframe (use browser_evaluate to access)

Automation detection

If site blocks automation:

1. Use --user-data-dir with existing browser profile
2. Use headed mode instead of headless
3. Try --extension mode with real browser

Flaky Test Prevention

Common causes:

• Race conditions: Tests proceed before app ready
• Unstable selectors: IDs change between renders
• Network unpredictability: API response time varies
• State contamination: Tests share state

Solutions:

• Always call browser_snapshot() before interacting
• Use stable selectors (data-testid, roles, labels)
• Wait for specific elements, not arbitrary timeouts
• Isolate tests with fresh browser contexts

Setup

For initial installation, see SETUP.md in this skill folder.

Requirements:

• Node.js 18+ with npx in PATH
• Chrome/Chromium for headed mode