Google Researcher vs OpenHeritage Public Search

In-depth architectural comparison of the Google Researcher and OpenHeritage Public Search 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 Researcher when:

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

Explore Google Researcher Details

Choose OpenHeritage Public Search when:

• You need dedicated capabilities in the Search & Data Extraction domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore OpenHeritage Public Search Details

Feature & Specification Comparison

Specification	Google Researcher Search & Data Extraction	OpenHeritage Public Search Search & Data Extraction
Summary	MCP server providing Google Search, web scraping, and multi-source research tools for AI assistants	Public search of genealogy, archives, photos, memorials, cemeteries, research, and repositories.
Category & Scope	Search & Data Extraction	Search & Data Extraction

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-researcher": {
      "command": "uvx",
      "args": [
        "web-researcher-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "openheritage-public-search": {
      "url": "https://openheritage.online/mcp"
    }
  }
}

Related MCP Server Comparisons