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

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

How do I install WebRun Browser Automation or Google Surf MCP 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 WebRun Browser Automation and Google Surf MCP free or paid?

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

Which MCP server has more tools and community activity?

WebRun Browser Automation lists 0 tools with 0 views and 0 GitHub stars. Google Surf MCP lists 22 tools with 1 views and 290 GitHub stars.

Can I use both WebRun Browser Automation and Google Surf MCP 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

WebRun Browser Automation vs Google Surf MCP

In-depth architectural comparison of the WebRun Browser Automation 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.

At a Glance & Executive Verdict

WebRun Browser Automation

Browser Automation · Local stdio

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

Google Surf MCP

Browser Automation · Local stdio

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

Verdict Summary: Choose WebRun Browser Automation if you need specialized Browser Automation tools running via a local process. Choose Google Surf MCP 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 WebRun Browser Automation 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 WebRun Browser Automation 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	W WebRun Browser Automation Browser Automation	Google Surf MCP Browser Automation
Summary	Run multi-step tasks in a real Chrome browser: persistent environments, live view, human takeover.	Google search via Playwright with a warm Chrome profile. No API key, no proxies.
Category & Scope	Browser Automation	Browser Automation

Tools & Capabilities Breakdown

WebRun Browser Automation Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Google Surf MCP Tools (22)

extract_mode

extract

project_id

limit

none

extract_limit

response_content

summary

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

WebRun Browser Automation Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "webrun-browser-automation": {
      "command": "npx",
      "args": [
        "-y",
        "webrun-browser-automation"
      ]
    }
  }
}

Google Surf MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to WebRun Browser Automation More alternatives to Google Surf MCP Browser Automation category hub Canonical compare URL