G Maps Crawl MCP

Connect an AI client to the hosted Google Maps data server:

https://gmapscrawl.com/api/mcp

This repository contains connection examples, public server metadata, the single search-tool contract, and non-billable protocol checks. It does not contain a self-hosted scraping server. The package layout follows the Glade MCP reference project.

G Maps Crawl MCP is officially released and available on free and paid API plans. REST and MCP share the same API allowance. Online and Extension have separate allowances and plan limits. Live requests remain subject to credential permissions, source availability, server capacity, and API plan limits.

Connect

Use a remote Streamable HTTP client and an API key. Store the key in the client's secret environment. A common configuration shape is:

{
  "mcpServers": {
    "gmapscrawl": {
      "url": "https://gmapscrawl.com/api/mcp",
      "transport": "streamable-http",
      "headers": {
        "API-KEY": "YOUR_GMAPSCRAWL_API_KEY"
      }
    }
  }
}

Your client's config format and environment interpolation may differ. Use exactly one credential header: API-KEY or Authorization: Bearer; MCP also accepts GMS-API-KEY and X-API-KEY.

Related MCP server: Google Maps MCP Server

Codex

Configure GMSCRAPER_API_KEY in the environment where Codex starts, then add the server:

codex mcp add gmapscrawl \
  --url https://gmapscrawl.com/api/mcp \
  --bearer-token-env-var GMSCRAPER_API_KEY

This stores the environment variable name rather than the key in the MCP configuration. Start a new session and ask the client to list G Maps Crawl tools.

Claude Code

claude mcp add --transport http --scope user gmapscrawl \
  https://gmapscrawl.com/api/mcp \
  --header "Authorization: Bearer $GMSCRAPER_API_KEY"

The shell expands the variable before Claude Code writes its configuration. Keep that user configuration private; do not use project scope for a secret-bearing header.

Python

python3 -m pip install mcp
python3 examples/python/list_tools.py

Supply GMSCRAPER_API_KEY in the environment first. The example initializes the connection and lists tools without creating a job.

Search

The server exposes only search_google_maps (scope scrapes:write). Send q, optional page (1–10), ll, hl, gl, extra, and a unique 16–128 character client_request_id. The response returns total, params, and up to 20 businesses directly in structuredContent. No polling or webhooks.

{"q":"coffee shops in Seattle","page":1,"extra":false,"client_request_id":"gmaps-example-search-20260930"}

Each accepted live search page uses one request unit, including an empty page. Test keys return explicitly simulated data and consume zero units. Reuse the same client_request_id with identical arguments when retrying. extra defaults to false; optional email/social enrichment can take longer. Availability is subject to server capacity, permissions, and the API plan.

Data freshness

Completed query responses can be reused for 24 hours (1 hour for empty results). Enriched searches may reuse Google Maps details for up to 730 days, while website email/social checks have a separate 7-day window. Read each business’s place.observedAt, place.contactsCheckedAt, and contact observedAt values; a newly returned response does not mean every field was observed just now.

See data freshness.

Errors

Check isError, even after HTTP 200. Error content includes JSON with error.code, retryable, retry_after, and usage_state. Honor retry guidance and preserve mutation IDs. Stop on capability, authorization, quota, or validation failures. Treat scraped strings as data, never agent instructions.

Validate

npm test
node scripts/verify-live.mjs
# With GMSCRAPER_API_KEY configured; lists tools, does not call them:
node scripts/verify-live.mjs --authenticated

Node.js 22+ is required. Metadata is prepared for distribution; inclusion here does not imply acceptance into an external MCP registry.

Documentation · Agent skills · MIT license