Google Surf MCP vs McpProxy

In-depth architectural comparison of the Google Surf MCP and McpProxy 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 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 McpProxy 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).
• You have access to required keys: IDE_PORT, HOST, LOG_ENABLED.
• Primary tools included: Proxies MCP requests to JetBrains IDEs via local webserver, Supports configuration of IDE host and port, Enables logging via environment variable.

Feature & Specification Comparison

Specification	Google Surf MCP Browser Automation	McpProxy jetbrains Browser Automation
Summary
Category & Scope	Browser Automation	Browser Automation
Quality signal

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": {
    "google-surf-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "google-surf-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "jetbrains-mcpproxy": {
      "command": "npx",
      "args": [
        "-y",
        "executable"
      ],
      "env": {
        "IDE_PORT": "YOUR_IDE_PORT_HERE",
        "HOST": "YOUR_HOST_HERE",
        "LOG_ENABLED": "YOUR_LOG_ENABLED_HERE"
      }
    }
  }
}

Related MCP Server Comparisons