Supasidebar MCP vs Google Surf MCP

In-depth architectural comparison of the Supasidebar MCP 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 Supasidebar 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: guide, list_spaces, list_links.

Explore Supasidebar MCP 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	Supasidebar MCP auspy Browser Automation	Google Surf MCP Browser Automation
Summary	Access and organize your open browser tabs, bookmarks, and recently opened links across every macOS browser from your AI client. Powered by the free SupaSidebar app.	Google search via Playwright with a warm Chrome profile. No API key, no proxies.
Category & Scope	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": {
    "auspy-supasidebar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "supasidebar-mcp"
      ]
    }
  }
}

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

Related MCP Server Comparisons