Provides tools for scraping Google Maps business data, including names, addresses, phones, emails, websites, ratings, review counts, categories, and coordinates.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@gmapsscraper Scrape coffee shops in Austin TX with emails"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP (Model Context Protocol) server for gmapsscraper.io — lets Claude, Cursor, Windsurf and any MCP client scrape Google Maps business data in plain conversation: names, addresses, phones, emails, websites, ratings, review counts, categories and coordinates.
"Find 50 dentists in Chicago with their emails" → done, right in your AI chat.
Tool | What it does |
| Search Google Maps and return business leads (blocks until done, ~30–120s) |
| Fire-and-forget version — returns a job id immediately |
| Fetch results of a previously started job |
| Check remaining credit balance |
Each scrape costs 2 credits; multiple keywords in one call cost the same. Free tier: 10 credits (5 searches, no credit card) — get an API key at gmapsscraper.io/dashboard.
Related MCP server: maps-scrapper
claude mcp add gmapsscraper -e GMAPSSCRAPER_API_KEY=your_key -- npx -y @gmapsscraper/mcpAdd to your MCP config (claude_desktop_config.json, .cursor/mcp.json, etc.):
{
"mcpServers": {
"gmapsscraper": {
"command": "npx",
"args": ["-y", "@gmapsscraper/mcp"],
"env": {
"GMAPSSCRAPER_API_KEY": "your_key"
}
}
}
}Installing from a plugin directory uses the bundled mcp.json, which
deliberately ships without an env block — the Open Plugins spec only expands
${PLUGIN_ROOT} and ${PLUGIN_DATA}, so a secret placeholder would be passed through
literally and the server would fail to authenticate.
Set the key in your own environment before starting the client:
# macOS / Linux — add to ~/.zshrc or ~/.bashrc
export GMAPSSCRAPER_API_KEY=your_key# Windows PowerShell
setx GMAPSSCRAPER_API_KEY "your_key"Restart the client afterwards so it picks up the variable. If a scrape returns an
auth error, run get_credits first — it fails fast and confirms whether the key
is being seen.
Requires Node.js ≥ 18. The server runs locally over stdio and talks to the gmapsscraper.io API — no other infrastructure involved.
"Scrape coffee shops in Austin TX with emails and give me a table"
"Find plumbers in Miami, then draft a cold email for the top 5 by rating"
"Start a scrape for 'wedding photographer in Denver CO', I'll check back later"
"How many gmapsscraper credits do I have left?"
title, address, phone, email, website, rating, reviews_count, category, latitude, longitude, google_maps_url, opening_hours
Results are capped at 100 businesses per response to keep your context tidy; the full CSV is always available from the dashboard.
📦 Node.js SDK — npm install @gmapsscraper/sdk (this server is built on it)
🐍 Python SDK — pip install gmapsscraper-sdk
Get the remaining gmapsscraper.io credit balance for the configured API key. Each scrape costs 2 credits. Free to call.
Inputs: no named parameters.
Check the status of a scrape job and fetch the business records once it is complete. Does not spend credits — safe to call repeatedly.
Inputs: job_id (required).
Search Google Maps and return business leads: name, address, phone, email, website, rating, reviews count, category, coordinates. Costs 2 credits per call — every call bills again (NOT idempotent, do not retry on your own). Always confirm with the user before spending credits. Multiple related keywords in one call cost the same 2 credits. Blocks until the scrape finishes (typically 30-120s). Be specific with keywords, e.g. "vegan restaurant in Brooklyn NY".
Inputs: keywords (required), lang, depth, email, +2 more.
Submit a Google Maps scrape job without waiting for it to finish. Costs 2 credits per call — every call bills again (NOT idempotent, do not retry on your own). Always confirm with the user before spending credits. Returns a job id — poll it later with get_scrape_results. Use this instead of scrape_google_maps for large areas or when the user wants to continue working meanwhile.
Inputs: keywords (required), lang, depth, email, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool has a clearly distinct purpose: async job submission, result polling, credit checking, and synchronous scraping. The overlap between start_scrape_job and scrape_google_maps is explicitly addressed in the descriptions, making ambiguity minimal.
All tool names follow a consistent verb_noun pattern with snake_case (start_scrape_job, get_scrape_results, get_credits, scrape_google_maps), making the naming predictable and readable.
With 4 tools, the server is well-scoped for a focused Google Maps scraping service. Each tool serves an essential function without unnecessary redundancy.
The tool set covers the core lifecycle: asynchronous job creation and retrieval, synchronous scraping, and credit management. Minor gaps like job cancellation or listing are not critical for the primary use case.
Turn Maps queries into lead lists: businesses, phones, websites, and reviews with async job control.
Find and enrich local businesses from Google Maps with owners, emails, phones, websites, and more.
Live Google Maps business search, review, and photo data for AI agents over MCP.
Real-time Google Maps local business leads, reviews, places & emails MCP. OAuth or API key.
