Browser Automation, Playwright & DevTools MCP Servers
Track breaking CLI flags, accessibility snapshot ref changes, and vision capabilities across Playwright MCP, Chrome DevTools MCP, Browserbase Stagehand, BrowserStack, WebdriverIO, and Appium MCP servers.
Browser MCP servers have high schema drift risk due to frequent snapshot element reference and capability flag updates (such as @playwright/mcp --caps=vision,pdf). Pin exact versions in CI and production agents. Across 13 tracked packages in Browser Automation, the average 90-day stability score is 76/100 with 9 high-drift packages. Most recent release: @browserstack/mcp-server v2.2.7 (2026-10-23).
Complete Browser Automation Comparison & Version Pin Matrix
Click any package to view `tools/list` schema diffs, watched symbols, and before/after migration code.
| Package | Registry | Live Version | Published | 90d Releases | Drift Risk | Stability | Recommended Exact Pin |
|---|---|---|---|---|---|---|---|
| @browserbasehq/stagehand Stagehand Browser Agent SDK | npm | v4.3.0 | 2026-10-20 | 10 | high | B (78) | npm install @browserbasehq/stagehand@4.3.0 |
| @playwright/mcp Playwright Official MCP Server | npm | v0.0.83 | 2026-09-28 | 5 | high | C+ (73) | npx -y @playwright/mcp@0.0.83 |
| @browserbasehq/mcp-server-browserbase Browserbase Stagehand MCP Server | npm | v2.4.3 | 2026-01-23 | 0 | high | B (78) | npx -y @browserbasehq/mcp-server-browserbase@2.4.3 |
| chrome-devtools-mcp Chrome DevTools Official MCP Server | npm | v1.12.0 | 2026-10-22 | 7 | medium | B+ (86) | npx -y chrome-devtools-mcp@1.12.0 |
| browser-use Browser Use (Python) | pypi | v0.13.11 | 2026-10-07 | 5 | high | C+ (73) | pip install "browser-use==0.13.11" |
| next-devtools-mcp Next Devtools MCP | npm | v0.4.0 | 2026-06-24 | 0 | high | C+ (73) | npx -y next-devtools-mcp@0.4.0 |
| @metamask/device-mcp Metamask Device MCP | npm | v0.5.0 | 2026-10-19 | 7 | high | C+ (73) | npx -y @metamask/device-mcp@0.5.0 |
| @browserstack/mcp-server Browserstack MCP Server | npm | v2.2.7 | 2026-10-23 | 26 | medium | B (78) | npx -y @browserstack/mcp-server@2.2.7 |
| @foldkit/devtools-mcp Foldkit Devtools MCP | npm | v0.25.0 | 2026-10-21 | 23 | high | C+ (69) | npx -y @foldkit/devtools-mcp@0.25.0 |
| rsbuild-plugin-vue-mcp Rsbuild Plugin Vue MCP | npm | v0.1.3 | 2026-09-06 | 4 | high | C+ (73) | npx -y rsbuild-plugin-vue-mcp@0.1.3 |
| @next-ai-drawio/mcp-server Next-ai-drawio MCP Server | npm | v0.4.6 | 2026-10-17 | 8 | high | C+ (73) | npx -y @next-ai-drawio/mcp-server@0.4.6 |
| appium-mcp Appium MCP | npm | v1.97.1 | 2026-10-12 | 37 | medium | B (78) | npx -y appium-mcp@1.97.1 |
| @wdio/mcp Wdio MCP | npm | v4.0.0 | 2026-10-08 | 5 | medium | B+ (86) | npx -y @wdio/mcp@4.0.0 |
Frequently Asked Questions: Browser Automation
Which Browser Automation packages have the highest schema drift risk?
Among the 13 tracked Browser Automation packages, 9 carry a HIGH schema drift risk rating, led by @browserbasehq/stagehand (v4.3.0), @playwright/mcp (v0.0.83), @browserbasehq/mcp-server-browserbase (v2.4.3), browser-use (v0.13.11), next-devtools-mcp (v0.4.0). Always pin exact versions in production.
What is the fastest-moving package in Browser Automation?
appium-mcp (Appium MCP) has shipped 37 releases in the last 90 days, with latest version v1.97.1 published on 2026-10-12.
How should engineering teams pin Browser Automation dependencies?
Browser MCP servers have high schema drift risk due to frequent snapshot element reference and capability flag updates (such as @playwright/mcp --caps=vision,pdf). Pin exact versions in CI and production agents.
Get Breaking-Change Alerts for Browser Automation
Monitor all 13 Browser Automation packages and receive instant migration snippets when tool schemas or exports shift.