Google Maps Scraper MCP Server Exposes search_google_maps Endpoint at /api/mcp

The service registers as a remote Model Context Protocol server that exposes only the search_google_maps tool. Clients configure .mcp.json with an Authorization header containing GMSCRAPER_API_KEY and receive JSON containing names, addresses, phones, ratings, and review counts. The endpoint negotiates protocol version on first POST and supports text/event-stream for incremental delivery.

Google Maps Terms of Service prohibit automated scraping outside the official Places API. The MCP wrapper bypasses browser sessions yet still consumes the same underlying data surface. Comparable prior services, such as the 2023 SerpApi Maps endpoint and Outscraper’s Maps crawler, faced rate-limit blocks and account suspensions within months of launch when query volume exceeded several thousand daily requests.

Operationally the server reduces context-switching for AI coding agents by injecting live geospatial records directly into Claude Code or Cursor sessions. It does not provide the full Places API field set and caps results at one page, limiting coverage to the first 20 listings returned by Google’s internal ranking. Production workloads therefore require an active Online subscription tier plus separate API entitlement.

Future integrations will depend on whether Anthropic’s MCP client library adds built-in retry and pagination handling; without those features, agents will hit the 20-record ceiling on any market larger than a single neighborhood.