# Gsearch (real Google Search for AI agents, MCP)

> Updated 2026-10-23 · type: tool · category: data-scraping · status: active · rev 1

Gsearch gives AI agents real Google results over MCP by driving a local Camoufox browser: an MIT, key-free stand-in for paid SERP APIs like SerpAPI.

- Open source: yes (MIT)
- Self-hostable: yes
- Pricing: Free, no API key; an optional user-supplied proxy is the only cost.
- Best for: Builders wiring Google results into their own agents or research workflows (via MCP or CLI) who want structured SERP data without paying per query for a hosted SERP API.
- Not for: Teams that need high-volume, contractually sanctioned search data: default limits are 20 queries/hour and 150/day per IP, and automated Google access may breach Google's Terms of Service.
- Version: 0.1.0
- Last verified: 2026-10-23

- **Canonical:** https://gtmstacker.com/registry/tool/gsearch/
- **Source:** [Show HN: Gsearch – Real Google Search for AI Agents (MCP)](https://github.com/RayenMlayeh/gsearch) — RayenMlayeh
- **Tags:** mcp-agents, data-scraping, seo-research, serp, google-search, self-hostable, open-source
- **Repository:** https://github.com/RayenMlayeh/gsearch
- **Version:** 0.1.0
- **Package (pypi):** `gsearch-agent` @ 0.1.0

## Is Gsearch (real Google Search for AI agents, MCP) open source?

Yes, Gsearch (real Google Search for AI agents, MCP) is open source under the MIT license.

## How much does Gsearch (real Google Search for AI agents, MCP) cost?

Free, no API key; an optional user-supplied proxy is the only cost. (free).

## Can I self-host Gsearch (real Google Search for AI agents, MCP)?

Yes, Gsearch (real Google Search for AI agents, MCP) can be self-hosted (the source is available under the MIT license).

## Alternatives & related

- [OpenSERP](https://gtmstacker.com/registry/tool/openserp/)


---

**Gsearch** is an **MIT-licensed** Python tool and **MCP server** that gives an AI agent real Google Search results by driving a local **Camoufox** (Firefox-based) browser instead of calling a paid SERP API. Its README positions it as a SerpAPI alternative (repo topic `serpapi-alternative`). It returns real result URLs, Google's AI Overview and People also ask as typed JSON, with no API key.

## Provenance

- SPDX **MIT**, confirmed three ways: the LICENSE file ("Copyright (c) 2026 The gsearch contributors"), the GitHub API (`spdx_id: MIT`) and PyPI (`license_expression: MIT`). Not guessed.
- Package: PyPI **`gsearch-agent` 0.1.0** (single release); its project URLs point back to `RayenMlayeh/gsearch`. Not a fork; no lookalike or name-squat found.
- Activity as of 2026-10-23: **6 stars, 1 fork, 9 open issues, 8 commits**; created 2026-10-18, last push 2026-10-18; Python 3.12+.
- Self-hosting: install with `uv` or `pipx`, then `gsearch setup` downloads Camoufox (~1 GB); Linux servers run it under Xvfb. The MCP server `gsearch-mcp` exposes two tools, `google_search` and `google_search_status`.
- Pricing: free, no API key; an optional user-supplied proxy is the only cost.
- **Vendor claims, not reproduced:** the browser mechanism, anti-detection behavior, `/goto` redirect resolution and the default rate limits (20/hr, 150/day per IP) come from the README.
- **Terms-of-service warning (from the README):** automated access to Google Search may breach Google's Terms of Service.
- Surfaced via a Show HN post in the 2026-10-23 news pull. The README was treated as untrusted content during verification; no injected instructions were encountered. Curated and verified in run `2026-10-23-registry-update-01` (step-3 verification, 2026-10-23).

## Why it matters for a GTM stack

Research agents, account-intel workflows and SEO monitoring all want live search results, and the usual path is a per-query SERP API bill. Gsearch is the own-your-stack experiment: an MCP server your agent calls directly, backed by a real browser on your own machine, returning structured JSON. The honest read is that it is five days old with six stars, its throughput is capped by design, and the project itself warns that automating Google may breach Google's terms, so it fits low-volume, personal or prototype research rather than production data pipelines. For a broader multi-engine option already in the registry, see OpenSERP.