Google Maps Scraper MCP

The Google Maps MCP for AI agents — OAuth in 30 seconds, no API keys. Extract B2B leads, emails, phones, ratings, reviews and social links from Google Maps directly inside Claude, Cursor, Codex, Windsurf, ChatGPT and any MCP-compatible AI client.

---

What this is

A Model Context Protocol server that gives any MCP-compatible AI agent a single, reliable way to pull structured data from Google Maps:

• 🏢 Businesses by keyword + location ("plumbers in Austin")
• 🔗 Specific Google Maps URLs (search pages or place pages)
• 📧 Verified emails and social links via optional website enrichment (charged only when an email is actually found)
• ⭐ Ratings, review counts, reviews, categories, opening hours, coordinates, phones, websites
• 🎯 Lead-quality scoring (0–100) for prioritising outreach

Backed by a battle-tested Apify actor with proxies, deduplication and robust parsing built in.

Why use it inside an AI agent?

Traditional Google Maps scrapers live in a separate dashboard. This one lives inside the agent: Claude, Cursor, Codex or any other MCP client can plan an outreach campaign, research competitors, or enrich a CRM — and actually pull the data in the same turn.

---

Two ways to install

| | Option A: Cloud MCP (OAuth) | Option B: Self-hosted (npm) | |--|--|--| | Install time | ~30 seconds | 2–3 minutes | | What you need | An Apify account (OAuth popup signs you in) | Node 18+ and an Apify API token | | Runs where | Apify Cloud | Your machine | | Best for | Most users — Claude, Cursor, Windsurf, VS Code, Codex | Self-hosted infra, air-gapped networks, advanced overrides | | Config | One URL | Command + token env var |

Not sure which one? Pick Option A. That's why it's first.

Client coverage at a glance (Option A)

| Client | Surface | Install path | |--------|---------|--------------| | Claude.ai | Web · Desktop · Cowork · iOS · Android | Settings → Connectors → Add custom connector | | ChatGPT | Web · Desktop | Settings → Connectors → Create (Pro/Team/Enterprise/Edu) | | Cursor | Desktop | One-click deeplink or ~/.cursor/mcp.json | | Claude Code | CLI | claude mcp add --transport http ... | | VS Code | Desktop | .vscode/mcp.json | | Windsurf | Desktop | ~/.codeium/windsurf/mcp_config.json | | OpenAI Codex CLI | CLI | ~/.codex/config.toml | | Others | — | LibreChat, Continue, Cline, Zed, Goose, Mistral Le Chat, Microsoft Copilot Studio, Sentinel… |

---

Option A — Cloud MCP (OAuth, recommended)

🔗 The one URL you need

https://mcp.apify.com?tools=khadinakbar/google-maps-leads-scraper

Paste this into any MCP-compatible client. On first call, a browser tab opens, you sign into Apify, and you're scraping. No tokens. No npm install. One setting covers Claude web, Claude Desktop, Cowork, mobile apps, ChatGPT web, Cursor, Windsurf, VS Code, Claude Code, Codex CLI and any other Streamable-HTTP MCP client.

New to Apify? Accounts are free and include $5 of credits — enough to scrape ~1,000 businesses before you pay a cent.

Web clients (nothing to install)

For users on Claude.ai (browser / Cowork / mobile app) and ChatGPT web — no desktop app, no config file, no CLI. Just add the connector URL in Settings and sign in.

Claude.ai (web, Cowork, mobile, Desktop — one setting for all)

1. Open Claude → profile icon → Settings → Connectors.
2. Scroll to the bottom and click "Add custom connector".
3. Paste:

   https://mcp.apify.com?tools=khadinakbar/google-maps-leads-scraper
   

4. Click Connect. A browser tab opens for Apify OAuth. Approve it.
5. You're done — the connector works across Claude web, Desktop, Cowork and mobile apps with a single setup.

Works on Free, Pro, Max, Team and Enterprise plans (Free is limited to 1 custom connector).

ChatGPT web (Pro, Team, Enterprise, Edu)

1. Open ChatGPT → Settings → Connectors (or Apps & Connectors → Add new connector on newer UIs). You may need to toggle Developer Mode in Advanced settings first.
2. Click Create / Add custom connector.
3. Fill in:
   • Name: Google Maps Scraper
   • Description: Scrape Google Maps businesses, emails, phones, reviews.
   • MCP server URL: https://mcp.apify.com?tools=khadinakbar/google-maps-leads-scraper
   • Authentication: OAuth (recommended) or Bearer with your Apify API token
4. Save. First call opens the Apify OAuth popup.

Not available on the Free plan.

Desktop / CLI clients

Config snippets below. Paste into the listed config file, save, restart the client.

Claude Desktop

Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Add:

{
  "mcpServers": {
    "google-maps-scraper": {
      "url": "https://mcp.apify.com?tools=khadinakbar/google-maps-leads-scraper"
    }
  }
}

Restart Claude Desktop. A browser tab opens for OAuth the first time. Done.

Cursor

One-click install:

Or edit ~/.cursor/mcp.json manually:

{
  "mcpServers": {
    "google-maps-scraper": {
      "url": "https://mcp.apify.com?tools=khadinakbar/google-maps-leads-scraper"
    }
  }
}

Then Cursor → Settings → MCP → Refresh. OAuth pops up on first call.

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "google-maps-scraper": {
      "url": "https://mcp.apify.com?tools=khadinakbar/google-maps-leads-scraper"
    }
  }
}

VS Code

Add to .vscode/mcp.json in your workspace or user settings:

{
  "servers": {
    "google-maps-scraper": {
      "type": "http",
      "url": "https://mcp.apify.com?tools=khadinakbar/google-maps-leads-scraper"
    }
  }
}

Claude Code

claude mcp add google-maps-scraper \
  --transport http \
  https://mcp.apify.com?tools=khadinakbar/google-maps-leads-scraper

OpenAI Codex CLI

Edit ~/.codex/config.toml:

[mcp_servers.google-maps-scraper]
url = "https://mcp.apify.com?tools=khadinakbar/google-maps-leads-scraper"

Other MCP clients

LibreChat, Continue, Cline, Zed, Goose, Roo Code, Mistral Le Chat connectors, Microsoft Copilot Studio and Sentinel — any client that accepts a Streamable HTTP MCP URL works with the same endpoint.

Prefer Bearer token over OAuth?

Any of the configs above also accepts a Bearer header. Skip OAuth, use your Apify API token:

{
  "mcpServers": {
    "google-maps-scraper": {
      "url": "https://mcp.apify.com?tools=khadinakbar/google-maps-leads-scraper",
      "headers": {
        "Authorization": "Bearer apify_api_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

Clients that don't speak Streamable HTTP yet

Wrap the URL with mcp-remote:

{
  "mcpServers": {
    "google-maps-scraper": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.apify.com?tools=khadinakbar/google-maps-leads-scraper"]
    }
  }
}

mcp-remote handles the OAuth flow for stdio-only clients.

---

Option B — Self-hosted (npm)

For when you want the server to run in your own process (air-gapped, internal network, heavy customisation).

Prerequisites

• Node 18+
• An Apify API token

Claude Desktop

{
  "mcpServers": {
    "google-maps-scraper": {
      "command": "npx",
      "args": ["-y", "google-maps-scraper-mcp"],
      "env": {
        "APIFY_TOKEN": "apif…[redacted]"
      }
    }
  }
}

Claude Code

claude mcp add google-maps-scraper \
  -e APIFY_TOKEN=apif…[redacted] \
  -- npx -y google-maps-scraper-mcp

Cursor / Windsurf / VS Code / Codex CLI

Same shape as Claude Desktop above — substitute the correct config path:

• Cursor: ~/.cursor/mcp.json
• Windsurf: ~/.codeium/windsurf/mcp_config.json
• VS Code: .vscode/mcp.json (use "type": "stdio")
• Codex CLI: ~/.codex/config.toml

Ready-to-paste examples live in examples/.

---

Tools exposed

The server exposes two tools. Descriptions are tuned for LLM discoverability — your agent picks the right one automatically.

search_google_maps

Search Google Maps by keyword + location. Best when the user describes a business type ("dentists", "SaaS agencies", "law firms").

| Parameter | Type | Default | Notes | |-----------|------|---------|-------| | searchQuery | string | required | e.g. "vegan restaurants" | | location | string | required | e.g. "Austin, TX" | | maxResults | integer | 20 | 1–500 | | enrichEmails | boolean | false | Visit business website to extract emails + socials | | minRating | number | 0 | 0–5 filter | | maxReviews | integer | 0 | Reviews per business (0 = none, fastest) | | language | enum | "en" | en, es, fr, de, it, pt, nl, pl, ru, ja, ko, zh-CN, ar, tr, hi |

scrape_google_maps_urls

Scrape specific Google Maps URLs — search pages or individual place pages. Best when the user already has links.

| Parameter | Type | Default | Notes | |-----------|------|---------|-------| | urls | string[] | required | 1–100 Google Maps URLs | | maxResults | integer | 20 | Across all URLs | | enrichEmails | boolean | false | Emails + socials | | maxReviews | integer | 0 | Reviews per business | | language | enum | "en" | Same options as above |

The cloud option exposes additional Apify meta-tools (actor discovery, docs lookup) automatically. The self-hosted npm package is deliberately scoped to just these two tools for a smaller surface area.

---

Example prompts

Drop these into Claude / Cursor / Codex once connected:

Find 30 independent coffee shops in Brooklyn with ratings above 4.3. Include phones and websites.

Get me the top 50 dental clinics in Dubai with verified emails for a cold-outreach campaign.

Scrape this Google Maps search: https://www.google.com/maps/search/solar+installers+in+Phoenix/ — 100 results, with emails.

Build a competitor list: the top 25 B2B SaaS agencies in London, show lead score + website + rating.

Enrich the first 10 businesses from https://www.google.com/m