microsoft/playwright-mcp

Prefer this fork if anti-bot bypass and an HTTP/OpenAPI interface are core requirements. Prefer upstream if you want the latest maintained Playwright MCP behavior, extension work, and lower operational risk.

Choose this fork if your main problem is multi-project browser automation with isolated state and persistent auth. Choose upstream if you want the most current, simplest, and best-maintained Playwright MCP baseline.

Choose this fork if you want broader browser-control and extraction features than upstream and can tolerate drift. Choose upstream if you want the actively maintained, safer default with recent fixes and packaging updates.

Choose this fork if you want a customized browser automation platform with extension, cloud, and research workflows built in. Choose upstream if you want the smallest, most current, easiest-to-track Playwright MCP server.

Choose this fork if you need customized Playwright MCP behavior, especially around extension-driven workflows and browser reuse. Choose upstream if you want the newest fixes, packaging, and the least maintenance risk.

Choose this fork if you want extra browser-automation features and are comfortable with significant divergence from upstream. Choose upstream if you want the most current, best-supported, lowest-risk Playwright MCP server.

Choose this fork if you value added extensibility and custom workflows more than staying close to upstream. Choose upstream if you want the safer path for compatibility, freshness, and lower maintenance burden.

Choose this fork if Electron support is the requirement and you want a package that installs more like a prebuilt distribution. Prefer upstream if you need the latest maintenance, broader client docs, and lower long-term upgrade risk.

Choose upstream unless you specifically need a static snapshot. This fork adds no visible capability and is materially behind, so it is a poor default for new adopters.