MCP Server Browser vs Playwritermcp MCP

A side-by-side look at the MCP Server Browser and Playwritermcp 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)Browser automation capabilities using Puppeteer, both support local and remote browser connection.67GreatAuth: no auth requiredPlaywritermcp MCP logoPlaywritermcp MCPBrowser Automation · Remote HTTP/SSEA paid remote MCP for AI agent browser MCP session, built to return verdicts, receipts, usage logs,48FairAuth: not declared

Verdict: choose MCP Server Browser for browser automation work as a local process; choose Playwritermcp MCP for browser automation over a hosted endpoint. 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.
  • Its auth model fits you: No auth required.
  • You want tools like browser_click, browser_close, browser_close_tab.
Explore MCP Server Browser

Playwritermcp MCP logoChoose Playwritermcp MCP when

  • You need dedicated capabilities in the Browser Automation domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like session_open, run_stateful_snippet, read_page_state.
Explore Playwritermcp MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP Server Browser logoMCP Server BrowserPlaywritermcp MCP logoPlaywritermcp MCP
CategoryBrowser AutomationBrowser Automation
Quality signal67/100 · Great48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars39,3680
Directory activity 6 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools234

Tools & capabilities

MCP Server Browser tools 23

  • browser_clickClick an element on the page, before using the tool, use `browser_get_clickable_elements` to get the index of the element, but not call `browser_get_clickable_elements` multiple times
  • browser_closeClose the browser when the task is done and the browser is not needed anymore
  • browser_close_tabClose the current tab
  • browser_evaluateExecute JavaScript in the browser console
  • browser_form_input_fillFill out an input field, before using the tool, Either 'index' or 'selector' must be provided
  • browser_get_clickable_elementsGet the clickable or hoverable or selectable elements on the current page, don't call this tool multiple times
  • browser_get_download_listGet the list of downloaded files
  • browser_get_markdownGet the markdown content of the current page
  • browser_get_textGet the text content of the current page
  • browser_go_backGo back to the previous page
  • browser_go_forwardGo forward to the next page
  • browser_hoverHover an element on the page, Either 'index' or 'selector' must be provided
  • +11 more on the listing page

Playwritermcp MCP tools 4

  • session_open
  • run_stateful_snippet
  • read_page_state
  • export_session_log

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": {
    "agent-infra-mcp-server-browser": {
      "command": "npx",
      "args": [
        "-y",
        "@agent-infra/mcp-server-browser"
      ]
    }
  }
}

Playwritermcp MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "playwritermcp-mcp": {
      "url": "https://playwritermcp.clauxel.com/mcp"
    }
  }
}

Frequently asked questions

MCP Server Browser is categorized under Browser Automation and uses a local stdio subprocess. Playwritermcp MCP belongs to Browser Automation and uses a remote HTTP/SSE transport. Pick MCP Server Browser for browser automation work and Playwritermcp 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 is listed as free. Auth: no auth required. Playwritermcp MCP 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 agent-infra-mcp-server-browser and playwritermcp-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 67/100 (Great) with 6 views, 0 installs and 39,368 GitHub stars. Playwritermcp MCP has 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.