Log inSubmit server
G Search MCP logo

G Search MCP

by jae-jae

Runs parallel Google searches through Playwright and returns structured JSON results for multiple queries.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install G Search MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "jae-jae-g-search-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "g-search-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y g-search-mcp

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

jae-jae/g-search-mcp MCP server runs Google searches for multiple queries in parallel through a Playwright-controlled Chromium browser. It opens multiple tabs in one browser instance and returns each query's results as structured JSON containing titles, links, and snippets. Search behavior can be adjusted with result limits, timeouts, locale, browser-state handling, and debug mode. Reach for it when an MCP client needs current Google search results across several keywords rather than a single manually opened search.

Use cases

  • Search several related keywords in parallel
  • Collect Google result titles, links, and snippets
  • Set a regional locale for search results
  • Inspect browser activity while debugging searches

Key features

  • Parallel multi-query Google searches
  • Playwright Chromium browser automation
  • Structured JSON search results
  • Configurable result limits and timeouts
  • Locale and browser-state controls
  • CAPTCHA detection with visible verification mode

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

20/20 checks healthy over the last 76d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · g-search-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars273Stargazers on the source repository.
npm downloads371Package downloads in the last 30 days.
Last commit1y agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How G Search MCP works

What jae-jae/g-search-mcp does

jae-jae/g-search-mcp MCP server exposes one MCP tool named search. It accepts an array of Google search queries and processes them in parallel, returning a JSON object that groups results by query. Each result can include a page title, URL, and search-result snippet.

The server fits the Search & Data Extraction category for workflows that need search-result discovery across multiple topics. For example, an agent can submit queries such as “machine learning” and “artificial intelligence” in one request, then inspect the returned result sets for links and summaries.

How it works

The server uses Playwright to control a Chromium browser. Parallel queries are handled through multiple tabs in the same browser instance. Search requests support a configurable maximum number of results per query, a page-loading timeout, and a locale value such as en-US or zh-CN.

Browser behavior includes user-like browsing patterns and automatic detection of CAPTCHA situations. When verification is required, the server can enable a visible browser window so a user can complete the verification step. Debug mode can also show the browser during a search, either through the startup flag or the individual tool request.

The returned structure contains a searches collection. Each entry identifies its original query and contains its corresponding results, making the output suitable for downstream parsing or comparison.

Setup and configuration

jae-jae/g-search-mcp MCP server requires Node.js 18 or newer and npm or Yarn. The quickest launch method is:

Terminal
npx -y g-search-mcp

Playwright Chromium must be installed separately on first use:

Terminal
npx playwright install chromium

For a source installation, clone the repository, install npm dependencies, install the browser with npm run install-browser, and build with npm run build. Development commands include npm run watch for automatic rebuilding and npm run inspector for MCP Inspector debugging.

Claude Desktop can start the server with an MCP configuration that uses npx as the command and passes -y g-search-mcp as its argument. The configuration file is located under the Claude application support directory on macOS or the %APPDATA%/Claude directory on Windows.

Tools and capabilities

The available search tool supports these parameters:

  • queries: Required array of search strings.
  • limit: Maximum results per query; the default is 10.
  • timeout: Page-load timeout in milliseconds; the default is 60,000.
  • noSaveState: Prevents browser-state saving when set to true; the default is false.
  • locale: Search locale, defaulting to en-US.
  • debug: Shows the browser for that request and overrides the command-line debug setting.

A startup --debug option enables visible-browser mode for the server. Agents can also request debug mode only for a particular search by setting the tool parameter.

Limitations and notes

Results depend on Google page availability, browser execution, locale, and any verification step encountered during browsing. The server is a search-results tool: the documented output contains result metadata and snippets, not full fetched page contents.

Chromium is an operational prerequisite even when the server is launched with npx. Slow pages may require increasing timeout, and searches targeting a different region should set an appropriate locale. No required environment variables are documented for running the server.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about G Search MCP

Run `npx -y g-search-mcp`, then install the required browser with `npx playwright install chromium`. The project also supports installation from source with npm.

Yes. The README provides Claude Desktop configuration using `npx` with `-y g-search-mcp` as the argument.

Call the `search` tool with the required `queries` array. The server searches the supplied queries in parallel and groups the results by query.

Set the `locale` parameter for the search region and `limit` for the maximum number of results per query. The defaults are `en-US` and 10 results.

Related MCP servers

All in Search & Data Extraction All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewG Search MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/jae-jae-g-search-mcp?style=directory)](https://allmcps.com/mcp/jae-jae-g-search-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/jae-jae-g-search-mcp"><img src="https://allmcps.com/api/badge/jae-jae-g-search-mcp?style=directory" alt="G Search MCP on AllMCPs" /></a>