MCP Server Browser vs Playwright MCP

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

MCP Server Browser logoMCP Server BrowserBrowser Automation · Local subprocess (stdio)The Open-Source Multimodal AI Agent Stack: Connecting Cutting-Edge AI Models and Agent Infra52GoodAuth: not declaredPlaywright MCP logoPlaywright MCPBrowser Automation · Local subprocess (stdio)Official Microsoft Playwright MCP server, enabling LLMs to interact with web pages through structured accessibility snapshots89ExcellentAuth: no auth required

Verdict: choose MCP Server Browser for browser automation work as a local process; choose Playwright MCP 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?

MCP Server Browser logoChoose MCP Server Browser when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a local stdio subprocess transport.
Explore MCP Server Browser

Playwright MCP logoChoose Playwright MCP 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 browser_close, browser_resize, browser_console_messages.
Explore Playwright MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Server Browser logoMCP Server BrowserPlaywright MCP logoPlaywright MCP
CategoryBrowser AutomationBrowser Automation
Quality signal52/100 · Good89/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars39,34438,407
Directory activity 2 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
ToolsNot listed25

Tools & capabilities

MCP Server Browser tools

No tool names declared yet. Check the project README from the listing page.

Playwright MCP tools 25

  • browser_closeClose the page
  • browser_resizeResize the browser window
  • browser_console_messagesReturns all console messages
  • browser_handle_dialogHandle a dialog
  • browser_emulate_mediaEmulate CSS media features for the page, for example switch between the light and dark color scheme. Omitted parameters are left unchanged; null clears an override.
  • browser_evaluateEvaluate JavaScript expression on page or element
  • browser_file_uploadUpload one or multiple files
  • browser_dropDrop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of "paths" or "data" must be provided.
  • browser_findSearch the accessibility snapshot of the current page for text or a regular expression. Returns matching snapshot nodes with a few lines of surrounding context (like search snippets), each shown under its path from the root of the tree, which is cheaper than capturing the whole snapshot when you only need to locate an element and its ref.
  • browser_fill_formFill multiple form fields
  • browser_press_keyPress a key on the keyboard
  • browser_typeType text into editable element
  • +13 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.

MCP Server Browser

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-server-browser": {
      "command": "npx",
      "args": [
        "-y",
        "@agent-tars/cli@latest"
      ]
    }
  }
}

Playwright MCP

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

Frequently asked questions

MCP Server Browser is categorized under Browser Automation and uses a local stdio subprocess. Playwright MCP belongs to Browser Automation and uses a local stdio subprocess. Pick MCP Server Browser for browser automation work and Playwright MCP 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.

MCP Server Browser has no declared pricing — check the project's own site. Playwright MCP is listed as free. Auth: no auth required. 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 mcp-server-browser and microsoft-playwright-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP Server Browser has a quality signal of 52/100 (Good) with 2 views, 0 installs and 39,344 GitHub stars. Playwright MCP has 89/100 (Excellent) with 6 views, 0 installs and 38,407 GitHub stars.