Playwright Alternatives: 4 MCP Servers Like Playwright

Playwright MCP lets AI assistants operate browsers using structured accessibility data. It suits agents that need persistent page context, interactive exploration, and browser inspection without a vision model.

Playwright alternatives compared

Playwright MCP exposes browser automation to AI clients through Playwright. Instead of requiring a model to interpret page pixels, it supplies structured accessibility information that an agent can inspect before choosing an action. The available controls cover navigation, clicks, keyboard input, forms, dropdowns, tabs, uploads, and drag operations. Inspection tools expose console output and network traffic, while screenshots provide a separate visual record. This combination supports exploratory browsing and testing workflows in which an assistant repeatedly examines a page and acts on its current structure. The README positions persistent browser context as a reason to choose the MCP interface for longer agent loops.

Ranked by shared tags × quality; ties: quality, non-monorepo stars, slug.

Playwright setup notes

Playwright MCP's stdio example needs a client that launches local processes.

Why switch from Playwright

1. Browserbase MCP Server

Playwright MCP and Browserbase MCP Server have no exact tool-name overlap in their recorded lists. Browserbase MCP Server lists 6 names absent from Playwright MCP, including act, end, extract. Moving from Playwright MCP to Browserbase MCP Server would also mean rechecking workflows using browser_click, browser_close, browser_console_messages, which appear only in Playwright MCP's list. Playwright MCP and Browserbase MCP Server both list node / stdio / Apache-2.0. Browserbase MCP Server's repository is archived; Playwright MCP's is not marked archived. Browserbase MCP Server's repository has 34,912 fewer stars than Playwright MCP (3,399 versus 38,311). Last pushes: Playwright MCP 2026-10-16; Browserbase MCP Server 2026-07-20.

Browserbase MCP Server overlaps Playwright on: browser-automation.

2. Playwright MCP Server

Playwright MCP and Playwright MCP Server have no exact tool-name overlap in their recorded lists. Playwright MCP Server lists 1 name absent from Playwright MCP, including playwright_resize. Moving from Playwright MCP to Playwright MCP Server would also mean rechecking workflows using browser_click, browser_close, browser_console_messages, which appear only in Playwright MCP's list. Playwright MCP and Playwright MCP Server both list node / stdio. Playwright MCP is listed under Apache-2.0, versus MIT for Playwright MCP Server. Playwright MCP Server's repository has 32,643 fewer stars than Playwright MCP (5,668 versus 38,311). Last pushes: Playwright MCP 2026-10-16; Playwright MCP Server 2025-12-13.

Playwright MCP Server overlaps Playwright on: playwright.

3. Browser Use MCP Server

Playwright MCP records node; Browser Use MCP Server records python. Playwright MCP and Browser Use MCP Server both list stdio. Playwright MCP is listed under Apache-2.0, versus MIT for Browser Use MCP Server. Browser Use MCP Server's repository has 37,465 fewer stars than Playwright MCP (846 versus 38,311). Last pushes: Playwright MCP 2026-10-16; Browser Use MCP Server 2026-05-20.

Browser Use MCP Server overlaps Playwright on: playwright.

4. Browser MCP

Playwright MCP and Browser MCP both list node / stdio / Apache-2.0. Browser MCP's repository has 31,118 fewer stars than Playwright MCP (7,193 versus 38,311). Last pushes: Playwright MCP 2026-10-16; Browser MCP 2025-04-24.

Browser MCP overlaps Playwright on: browser-automation.