What is the key difference between Google Surf MCP and Browser Use?

Google Surf MCP belongs to the Browser Automation category with local stdio execution, while Browser Use belongs to the Browser Automation category with local stdio execution.

How do I install Google Surf MCP or Browser Use in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Google Surf MCP and Browser Use free or paid?

Google Surf MCP operates under a Free / Open Source model (No auth required). Browser Use operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Google Surf MCP lists 22 tools with 1 views and 290 GitHub stars. Browser Use lists 0 tools with 0 views and 115,766 GitHub stars.

Can I use both Google Surf MCP and Browser Use together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Google Surf MCP vs Browser Use

In-depth architectural comparison of the Google Surf MCP and Browser Use 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.

At a Glance & Executive Verdict

Google Surf MCP

Browser Automation · Local stdio

Quality: 61/100 (Good) | Auth: No auth required

Browser Use

Browser Automation · Local stdio

Quality: 49/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Google Surf MCP if you need specialized Browser Automation tools running via a local process. Choose Browser Use if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

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

Choose Browser Use 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 Browser Use Details

Feature & Specification Comparison

Specification	Google Surf MCP Browser Automation	Browser Use Browser Automation
Summary	Google search via Playwright with a warm Chrome profile. No API key, no proxies.	Control a real Chrome browser to complete any task: fill forms, extract data, book flights.
Category & Scope	Browser Automation	Browser Automation

Tools & Capabilities Breakdown

Google Surf MCP Tools (22)

extract_mode

extract

project_id

limit

none

extract_limit

response_content

summary

requested

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).

Google Surf MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Browser Use Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "browser-use": {
      "command": "uvx",
      "args": [
        "browser-use"
      ]
    }
  }
}

Frequently Asked Questions

Google Surf MCP is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Browser Use belongs to Browser Automation using local stdio subprocess. Select Google Surf MCP when you need capabilities focused on browser automation and Browser Use when you require tools for browser automation.