Is Google Researcher free?

Yes, Google Researcher is free to use.

How do I install Google Researcher?

Google Researcher is a local plugin. Install it using npm package: google-researcher-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Google Researcher safe to use?

Yes. Google Researcher passed MCP Marketplace's automated security scan with a score of 9.8/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Google Researcher need?

Google Researcher requires the following credentials or environment variables: GOOGLE_CUSTOM_SEARCH_API_KEY, GOOGLE_CUSTOM_SEARCH_ID. You can find setup instructions on the server detail page.

What AI apps work with Google Researcher?

Google Researcher uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Google Researcher MCP Server

by User

Developer ToolsLow Risk9.8Local

Free

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

About

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

Security Report

9.8

Low Risk9.8Low Risk

Valid MCP server (3 strong, 1 medium validity signals). 1 known CVE in dependencies Package registry verified. Imported from the Official MCP Registry.

4 files analyzed · 2 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Google Custom Search API keyRequired

Environment variable: GOOGLE_CUSTOM_SEARCH_API_KEY

Google Programmable Search Engine IDOptional

Environment variable: GOOGLE_CUSTOM_SEARCH_ID

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-zoharbabin-google-researcher": {
      "env": {
        "GOOGLE_CUSTOM_SEARCH_ID": "your-google-custom-search-id-here",
        "GOOGLE_CUSTOM_SEARCH_API_KEY": "your-google-custom-search-api-key-here"
      },
      "args": [
        "-y",
        "google-researcher-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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 Issue	Resolution in web-researcher-mcp
#108 — Orphan detection fails via npx	Go binary has native process lifecycle (EOF/SIGPIPE) — no npm wrapper
#107 — Google discontinuing 'entire web' search	Eight providers (Brave, Serper, SearXNG, SearchAPI, Tavily, Exa, DuckDuckGo + Google PSE for lenses) with automatic fallback
#55 — Support alternative search engines	Multiple engines behind one interface, plus a zero-config DuckDuckGo default
#72 — Add Redis caching	Hybrid cache: memory + AES-encrypted disk + optional Redis
#40 — Split server.ts into modules	Fully 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.