English Français العربية

io.github.zoharbabin/google-researcher

Official registry Archived Search and web

MCP server providing Google Search, web scraping, and multi-source research tools for AI assistants

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package google-researcher-mcp
Claude Code 
claude mcp add google-researcher -e 'GOOGLE_CUSTOM_SEARCH_API_KEY=<your google_custom_search_api_key>' -e 'GOOGLE_CUSTOM_SEARCH_ID=<GOOGLE_CUSTOM_SEARCH_ID>' -- node -y google-researcher-mcp@6.3.3
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "google-researcher": {
            "command": "node",
            "args": [
                "-y",
                "google-researcher-mcp@6.3.3"
            ],
            "env": {
                "GOOGLE_CUSTOM_SEARCH_API_KEY": "<your google_custom_search_api_key>",
                "GOOGLE_CUSTOM_SEARCH_ID": "<GOOGLE_CUSTOM_SEARCH_ID>"
            }
        }
    }
}

Environment variables

  • GOOGLE_CUSTOM_SEARCH_API_KEY required secret Google Custom Search API key
  • GOOGLE_CUSTOM_SEARCH_ID required Google Programmable Search Engine ID

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. google-researcher-mcp — DEPRECATED
  2. Migrate in one line
  3. Why the Rewrite?
  4. Links

google-researcher-mcp — DEPRECATED

⚠️ This project has been superseded by web-researcher-mcp.

A complete rewrite in Go: same tools, but it cites real sources and stays honest — citation verification, retraction flagging, eight search providers behind one interface, and a single signed static binary. No Node.js, no npm.

Migrate in one line

Your API keys and tool calls don't change — only how the server is launched. Pick whichever you prefer (no Node required):

# macOS / Linux — installs the binary and registers it with Claude Code automatically:
curl -fsSL https://raw.githubusercontent.com/zoharbabin/web-researcher-mcp/main/install.sh | sh

# Windows (PowerShell):
powershell -ExecutionPolicy Bypass -c "irm https://raw.githubusercontent.com/zoharbabin/web-researcher-mcp/main/install.ps1 | iex"

# Python users (uv) — run with no install:
uvx web-researcher-mcp
Before / after (MCP client config)

The config keeps the same shape — swap the command/args, keep your env:

// BEFORE — google-researcher-mcp (npx / Node)
{
  "mcpServers": {
    "google-researcher": {
      "command": "npx",
      "args": ["-y", "google-researcher-mcp"],
      "env": { "GOOGLE_CUSTOM_SEARCH_API_KEY": "…", "GOOGLE_CUSTOM_SEARCH_ID": "…" }
    }
  }
}

// AFTER — web-researcher-mcp (installed binary; or use "uvx" + args ["web-researcher-mcp"])
{
  "mcpServers": {
    "web-researcher": {
      "command": "web-researcher-mcp",
      "env": { "GOOGLE_CUSTOM_SEARCH_API_KEY": "…", "GOOGLE_CUSTOM_SEARCH_ID": "…" }
    }
  }
}

Don't run both at once — they register identical tool names. Remove the google-researcher entry before adding web-researcher.

→ Full migration guide

Your existing GOOGLE_CUSTOM_SEARCH_API_KEY and GOOGLE_CUSTOM_SEARCH_ID work unchanged.

Why the Rewrite?

Open IssueResolution in web-researcher-mcp
#108 — Orphan detection fails via npxGo binary has native process lifecycle (EOF/SIGPIPE) — no npm wrapper
#107 — Google discontinuing 'entire web' searchEight providers (Brave, Serper, SearXNG, SearchAPI, Tavily, Exa, DuckDuckGo + Google PSE for lenses) with automatic fallback
#55 — Support alternative search enginesMultiple engines behind one interface, plus a zero-config DuckDuckGo default
#72 — Add Redis cachingHybrid cache: memory + AES-encrypted disk + optional Redis
#40 — Split server.ts into modulesFully modular Go architecture (one package per concern)

Plus what's new: verify_citation and audit_bibliography (catch fabricated/retracted citations), academic / patent / SEC-filing / US-case-law / economic / clinical-trial search, and authority-weighted search lenses.

Frequently asked questions

What is io.github.zoharbabin/google-researcher?

MCP server providing Google Search, web scraping, and multi-source research tools for AI assistants

How do I install io.github.zoharbabin/google-researcher?

It runs on your machine. In Claude Code: claude mcp add google-researcher -e 'GOOGLE_CUSTOM_SEARCH_API_KEY=<your google_custom_search_api_key>' -e 'GOOGLE_CUSTOM_SEARCH_ID=<GOOGLE_CUSTOM_SEARCH_ID>' -- node -y google-researcher-mcp@6.3.3. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.zoharbabin/google-researcher need an API key?

Yes. It expects GOOGLE_CUSTOM_SEARCH_API_KEY, GOOGLE_CUSTOM_SEARCH_ID, which you set in its configuration.

Is io.github.zoharbabin/google-researcher open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.zoharbabin/google-researcher?

It is published by zoharbabin. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.