Comments
>log in to commentI built google-browser-scraper to give developers a self‑hosted SerpApi alternative that runs a real browser behind your own proxy. It exposes an HTTP API and an MCP server for easy integration. Let me know what you think!
Open-source tool that scrapes Google Search results using a real browser and sticky proxies, returning SerpApi-style JSON.
- for
- Developers and AI agents needing reliable Google search data.
- pricing
- free
- license
- MIT
Key features
- Real-browser execution — Uses Chrome/Playwright to render JavaScript and interact with Google as a human would.
- Sticky proxy support — Works with residential proxies that keep session state across requests.
- Explicit captcha/block reporting — Captchas and blocks are returned as distinct verdicts instead of empty results.
- SerpApi-like output schema — Provides organic results, ads, related questions, and metadata in a familiar JSON format.
- CLI, HTTP API and MCP server — Can be run as a command-line tool, local API server, or AI-agent compatible MCP service.
- Docker image — Official Docker build for easy deployment and testing.
- Link resolution handling — Resolves Google’s encrypted redirects via short-lived proxy sessions.
- Proxy session diagnostics — Reports bytes used and session info for each query, with a ‘doctor’ command to test the environment.
Use cases
- Gather Google search results for training LLMs or AI agents.
- Collect SERP data for SEO analysis while handling captchas gracefully.
- Run automated market research queries behind residential proxies.
- Provide search results to a chatbot via the MCP interface.
Google Browser Scraper vs alternatives
 Google Browser Scraper |  Algolia |  Meilisearch |  Typesense |  Elasticsearch | |
|---|---|---|---|---|---|
| Best for | Browser-based Google search scraping | Hosted search-as-a-service | Self-hosted search engine | Typo-tolerant search indexing | Enterprise search and analytics |
| Pricing | Free | Subscription | Free | Free | Subscription |
| DevHunt upvotes | 1 | 0 | 0 | 0 | 0 |
| Launched | Oct 2026 | — | — | — | — |
- Google Browser Scraper vs Algolia: Algolia offers a hosted search API, not a browser-based scraper of Google results.
- Google Browser Scraper vs Meilisearch: Meilisearch is an open-source search engine you host yourself, unrelated to Google SERP scraping.
- Google Browser Scraper vs Typesense: Typesense provides typo-tolerant search indexing, not Google result extraction via a browser.
- Google Browser Scraper vs Elasticsearch: Elasticsearch is a distributed search and analytics engine, not a tool for scraping Google SERPs.
Google Browser Scraper FAQ
Do I need a proxy to use Google Browser Scraper?+
A residential proxy with sticky sessions is required for reliable results, but you can run without a proxy using the --no-proxy flag.
What format does the tool return?+
Results are returned as JSON objects per page, following a SerpApi-like schema, with optional CSV output.
Can I run the scraper as a web service?+
Yes, use the 'serve' command to start a local HTTP API that serves the same JSON format.
Is the tool compatible with AI agents?+
It provides an MCP server exposing a google_search(query, pages) tool that agents can call.
What platforms are supported?+
It runs on Windows, Linux (experimental) and Docker; requires Python 3.10+ and Chrome.
Is this a free Google Search API?+
No, it is a browser-based collector; you must comply with Google’s terms and use your own proxies.
Summarized by DevHunt from pypi.org · Oct 13, 2026. Details may change; check the official site.
