Public Browser vs Google Surf MCP

In-depth architectural comparison of the Public Browser and Google Surf MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Public Browser when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Public Browser Details

Choose Google Surf MCP when:

• You need dedicated capabilities in the Browser Automation domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: extract_mode, extract, project_id.

Explore Google Surf MCP Details

Feature & Specification Comparison

Specification	Public Browser Browser Automation	Google Surf MCP Browser Automation
Summary	The most token-efficient MCP server for Chrome automation — a Playwright MCP alternative.	Google search via Playwright with a warm Chrome profile. No API key, no proxies.
Category & Scope	Browser Automation	Browser Automation

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "public-browser": {
      "command": "npx",
      "args": [
        "-y",
        "public-browser@latest"
      ]
    }
  }
}

{
  "mcpServers": {
    "google-surf-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "google-surf-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons