mcpField
G
Google Researcher MCP Server

Google Researcher MCP Server

Local
github.com/zoharbabinData & Analytics36Updated 20w ago

About Google Researcher MCP Server

Google Researcher MCP Server is an open-source MCP server for Google Search–based research, now deprecated. Its README states it has been superseded by web-researcher-mcp, a Go rewrite with the same tools.

Key features

  1. 01Google Search-enhanced research tools
  2. 02YouTube and web scraping
  3. 03LLM-driven content synthesis
  4. 04Persistent caching
  5. 05STDIO and HTTP SSE transports

Use cases

  1. 01Retrieving sources through Google Search for AI agents
  2. 02Maintaining legacy deployments before migrating

MCP support

This project is an MCP server that exposes search, scraping and synthesis research tools to MCP clients over STDIO or HTTP SSE.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

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.


Links

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.