Playwright MCP Server for Windsurf: Setup & Config

What you can do with Playwright in Windsurf

Pick it for Playwright automation with device presets, test generation, and automatic browser setup.

• Capture screenshots while investigating a web application.
• Scrape page content or run JavaScript in a real browser.

Before you start: Playwright in Windsurf

• An MCP-compatible client
• npm/npx tooling
• Playwright browser binaries, installed automatically if missing

This is the documented stdio configuration. HTTP mode uses --port 8931 and requires type: http in the client. The server binds to localhost; the README describes SSH tunneling for remote access.

Playwright Windsurf configuration

1. Choose Windsurf configuration scope

   For Playwright MCP Server, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

2. Add Playwright MCP Server to Windsurf

   Use the mcp-playwright entry below in mcpServers. Keep Playwright MCP Server's documented stdio connection fields and your other Windsurf entries.

3. Check Playwright MCP Server in Windsurf

   Playwright MCP Server: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

{
  "mcpServers": {
    "mcp-playwright": {
      "command": "npx",
      "args": [
        "-y",
        "@executeautomation/playwright-mcp-server"
      ],
      "env": {}
    }
  }
}

Playwright tools available to Windsurf

Playwright's stored tool list documents 1 tool; compare it with Windsurf's connected tool list, because the stored list is not a live check.

playwright_resize

After refreshing Playwright in Windsurf settings, check Cascade's tool list for playwright_resize.

Change browser dimensions or select a device preset and orientation.

Playwright: full stored tool descriptions

Troubleshooting Playwright in Windsurf

• Check npx @executeautomation/playwright-mcp-server (Node.js/npm) on the machine running Windsurf's MCP integration for Playwright MCP Server; refresh MCP and inspect Cascade's tools.
• Playwright MCP Server uses stdio here: Windsurf must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: HTTP clients must explicitly set their transport type correctly.
• Known limitation: The HTTP service binds locally; remote access needs an additional approach such as SSH tunneling.
• General Windsurf troubleshooting lives in the /clients/windsurf guide.

Frequently asked questions