Playwright MCP Server vs MCP Browser Dev Tools

A side-by-side look at the Playwright MCP Server and MCP Browser Dev Tools MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Playwright MCP Server logoPlaywright MCP ServerBrowser Automation · Local subprocess (stdio)An MCP server using Playwright for browser automation and webscrapping68GreatAuth: no auth requiredMCP Browser Dev Tools logoMCP Browser Dev ToolsBrowser Automation · Local subprocess (stdio)Browser MCP server for AI agents: batch actions, waits, and checks into one call on Chrome, Edge, or Firefox (CDP and WebDriver BiDi)53GoodAuth: not declared

Verdict: choose Playwright MCP Server for browser automation work as a local process; choose MCP Browser Dev Tools for browser automation as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Playwright MCP Server logoChoose Playwright MCP Server when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like start_codegen_session, end_codegen_session, get_codegen_session.
Explore Playwright MCP Server

MCP Browser Dev Tools logoChoose MCP Browser Dev Tools when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like browser_status, ensure_browser, launch_browser.
Explore MCP Browser Dev Tools

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPlaywright MCP Server logoPlaywright MCP ServerMCP Browser Dev Tools logoMCP Browser Dev Tools
CategoryBrowser AutomationBrowser Automation
Quality signal68/100 · Great53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars5,6691
Directory activity 5 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools3345

Tools & capabilities

Playwright MCP Server tools 33

  • start_codegen_sessionStart a new code generation session to record Playwright actions
  • end_codegen_sessionEnd a code generation session and generate the test file
  • get_codegen_sessionGet information about a code generation session
  • clear_codegen_sessionClear a code generation session without generating a test
  • playwright_navigateNavigate to a URL
  • playwright_screenshotTake a screenshot of the current page or a specific element
  • playwright_clickClick an element on the page
  • playwright_iframe_clickClick an element in an iframe on the page
  • playwright_iframe_fillFill an element in an iframe on the page
  • playwright_fillfill out an input field
  • playwright_selectSelect an element on the page with Select tag
  • playwright_hoverHover an element on the page
  • +21 more on the listing page

MCP Browser Dev Tools tools 45

  • browser_status
  • ensure_browser
  • launch_browser
  • list_tabs
  • new_tab
  • close_tab
  • attach_tab
  • detach_tab
  • list_sessions
  • navigate
  • reload
  • click
  • +33 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Playwright MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "executeautomation-playwright-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@executeautomation/playwright-mcp-server"
      ]
    }
  }
}

MCP Browser Dev Tools

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-browser-dev-tools": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-browser-dev-tools"
      ]
    }
  }
}

Frequently asked questions

Playwright MCP Server is categorized under Browser Automation and uses a local stdio subprocess. MCP Browser Dev Tools belongs to Browser Automation and uses a local stdio subprocess. Pick Playwright MCP Server for browser automation work and MCP Browser Dev Tools for browser automation.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Playwright MCP Server is listed as free. Auth: no auth required. MCP Browser Dev Tools has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add executeautomation-playwright-mcp-server and mcp-browser-dev-tools as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Playwright MCP Server has a quality signal of 68/100 (Great) with 5 views, 0 installs and 5,669 GitHub stars. MCP Browser Dev Tools has 53/100 (Good) with 1 views, 0 installs and 1 GitHub stars.