Menu

Playwright MCP v0.0.73: How to Configure Browser Paths via Environment Variables
🖼️

Playwright MCP v0.0.73: How to Configure Browser Paths via Environment Variables

DEV Community·Anton Gulin·6 months ago
#T85Jo2Bh
#mcp#ai#automation#environment#playwright
Reading 0:00
15s threshold

This post was originally published on anton.qa . The canonical version lives there.

Playwright MCP v0.0.73 fixes a critical gap where extension channels and executable paths could not be resolved from CI/CD environment variables.

If you run Playwright MCP in Docker, Kubernetes, or ephemeral CI workers, this release removes a class of environment-specific debugging that typically consumes 15–30 minutes per incident.

What changed

Two interconnected bug fixes:

Extension channel and executablePath now resolve from CLI flags and environment variables ( #40572 )

--browser channel flags now propagate on --extension paths ( #40567 )

Combined, these changes mean your Playwright MCP setup can now be fully environment-driven.

The pattern

export PLAYWRIGHT_BROWSERS_CHANNEL = chromium export PLAYWRIGHT_EXTENSION_PATH = /path/to/browser-extension npx playwright test

Enter fullscreen mode

Exit fullscreen mode

The resolution hierarchy is now:

CLI flags (highest priority)

Environment variables

Config file…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.