๐Ÿ“ Google Maps MCP โ€” AI Lead Gen & Search avatar

๐Ÿ“ Google Maps MCP โ€” AI Lead Gen & Search

Pricing

from $10.00 / 1,000 results

Go to Apify Store
๐Ÿ“ Google Maps MCP โ€” AI Lead Gen & Search

๐Ÿ“ Google Maps MCP โ€” AI Lead Gen & Search

MCP server for AI assistants to search Google Maps businesses, extract leads with emails and phone numbers, get reviews, and analyze local competition. Works with Claude, Cursor, and MCP clients.

Pricing

from $10.00 / 1,000 results

Rating

0.0

(0)

Developer

Stephan Corbeil

Stephan Corbeil

Maintained by Community

Actor stats

0

Bookmarked

6

Total users

3

Monthly active users

6 hours ago

Last modified

Share

๐Ÿค– Google Maps MCP Server โ€” Local Business + Geocoding Tools for AI Agents

Plug Google Maps + Yelp scraping into Claude, ChatGPT, Cursor, or any MCP-compatible AI agent. A drop-in alternative to wiring Google Maps Places API directly into your agent, or paying for Mapbox MCP โ€” ships as an Apify Actor that exposes structured tools for search_places, place_details, geocode_address, reverse_geocode, and list_reviews.

Why This MCP Server Beats Direct Places API Wiring, Mapbox MCP & Custom Agent Plumbing

FeatureNexGenData Google Maps MCPGoogle Maps Places API (direct)Mapbox MCPCustom-built agent tool
CostPay-per-event, no subscription$17 โ€“ $32 per 1,000 callsMapbox plan tierEngineering time
MCP-ready out of the boxYes โ€” Apify MCP endpointNo โ€” wire SDK yourselfYesBuild it
Search + details + reviews + geocodeYes โ€” one tool surfaceMultiple endpoints + billingLimitedBuild them
AuthApify tokenGoogle Cloud API key + billingMapbox tokenWhatever you wire
Rate-limit handlingInternal proxy poolQuotas per projectPlan-gatedYou handle it
Output schemaStable JSON for AI agentsRaw Places API schemaMapbox schemaWhatever you define
Yelp coverage includedYes (via sister Yelp scraper handoff)NoNoBuild it
Time-to-first-tool-call< 5 minutesBilling + project setup + SDKSignup + planDays

Most AI-agent builders pick this MCP because it is cheaper than Places API per-call billing, simpler than writing a custom MCP shim, and broader than Mapbox's geocoding-first scope โ€” you get the full local-business lookup surface (places + reviews + hours + phone + website) as one MCP tool group.

What This MCP Exposes

The actor publishes the following MCP tools to your agent:

  • search_places(query, location, max_results) โ€” keyword + location search
  • place_details(place_id) โ€” full record for a Google place_id
  • list_reviews(place_id, max_reviews) โ€” reviews with author / rating / date / text
  • geocode_address(address) โ€” string โ†’ lat / long + structured components
  • reverse_geocode(lat, lng) โ€” lat / long โ†’ best-match address
  • nearby_places(lat, lng, type, radius) โ€” places within a radius by category
  • autocomplete(query, location) โ€” Google Maps autocomplete suggestions

Each tool returns structured JSON conformant to a stable MCP schema your agent can rely on.

Use Cases

  • AI travel agents โ€” "find me three highly-rated ramen places near my hotel" โ€” the agent calls search_places + list_reviews and synthesizes
  • AI sales SDRs โ€” "build me a list of every dental office in Austin TX with a website" โ€” search_places + place_details
  • Customer-support bots โ€” resolve "what's the closest store with stock" by nearby_places over your branch list
  • Real-estate buyer agents โ€” enrich a listing with nearby_places(type=school) and place_details
  • Logistics planners โ€” batch-geocode a CSV of addresses with geocode_address
  • Local-SEO research bots โ€” audit competitor ratings + review velocity via list_reviews
  • Voice / chat assistants โ€” power "near me" intents without sending the user out to Google Maps

Quick Start (MCP)

Configure Claude Desktop / Cursor / any MCP-compatible agent to use this Apify Actor as an MCP server:

{
"mcpServers": {
"google-maps-nexgendata": {
"url": "https://api.apify.com/v2/acts/nexgendata~google-maps-mcp-server/runs",
"auth": {"token": "YOUR_APIFY_TOKEN"}
}
}
}

Or call it directly as an Apify Actor:

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("nexgendata/google-maps-mcp-server").call(run_input={
"tool": "search_places",
"query": "coffee shop in seattle wa",
"max_results": 20,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item.get("name"), item.get("rating"))

Pricing

Pay-per-event. Small Actor Start fee plus per-tool-call fee. No monthly minimum, no seat fee. Stop paying the moment your agent stops calling.

Use caseActor
Underlying Google Maps places scraperGoogle Maps Scraper
Yelp business scraperYelp Business Scraper
Finance API surface for AI agentsFinance MCP Server
News + media monitoring for AI agentsNews MCP Server
Sports + scoreboard MCP for AI agentsSports MCP Server
Real-estate API for AI agentsReal Estate MCP Server
Developer-tool API (GitHub / npm / PyPI) for AI agentsDeveloper Tools MCP Server
Academic-research MCP (arXiv / Scholar)Academic Research MCP Server
Detect hiring signals from local businessesHiring Signal Detector
Bulk B2B leads finderB2B Leads Finder

FAQ

Drop-in for Google Maps Places API? For the typical "find a business + show details + show reviews" agent flow, yes. The MCP layer means you never write Places API HTTP code โ€” your agent calls a typed tool and gets back stable JSON.

Does it handle multiple regions? Yes โ€” global. Same locale support as Google Maps itself.

Is the schema stable for AI agents? Yes โ€” each tool returns a stable JSON shape with documented field names so your prompt can rely on the schema across versions.

Auth? Apify token only. No Google Cloud billing project required.

How is this different from the underlying scraper? The scraper actor is for batch ETL โ€” you give it a query, it fills a dataset. The MCP server is for live AI-agent calls โ€” your agent calls a tool, gets a structured response in the request-response cycle.

Cost? Pay-per-event โ€” you only pay for the tool calls your agent actually makes. No monthly minimum.

Can I combine it with Yelp? Yes โ€” our recommended pattern is to use Google Maps MCP for primary lookup and Yelp Business Scraper for cross-validation on US listings.

About NexGenData

NexGenData publishes 260+ buyer-intent actors covering SEC filings, YC alumni, lead generation, competitive intelligence, stock fundamentals across 30+ exchanges, and more. All pay-per-result. Browse the full catalog at https://apify.com/nexgendata?fpr=2ayu9b


How NexGenData Pricing Works

Every NexGenData actor uses pay-per-event pricing โ€” you only pay for results that actually land in your dataset. No monthly minimum, no seat fees, no surprise overage bills.

  • Actor Start: a single-event charge each time you spin the actor up (scaled to memory size)
  • Result: charged per item written to the default dataset
  • No charge for retries, internal proxy rotation, or failed sub-requests โ€” those are absorbed by the platform

If you only need the data once a quarter, you only pay once a quarter. If you scale to millions of records, the unit cost stays the same.

Apify Platform Bonus

New to Apify? Sign up with the NexGenData referral link โ€” you get free platform credits on signup (enough for several thousand free results) and you help fund the maintenance of this actor fleet.

Integration Surface

Every actor in the NexGenData catalog can be triggered from:

  • Apify console โ€” point-and-click run
  • Apify API โ€” REST + webhooks
  • Apify Python / JS SDKs โ€” programmatic batch
  • Zapier, Make.com, n8n โ€” official integrations
  • MCP โ€” many actors are exposed as MCP tools for Claude / ChatGPT / Cursor agents
  • Schedules โ€” built-in cron for daily / weekly / monthly runs
  • Webhooks โ€” POST results to any HTTPS endpoint on dataset write

Support

NexGenData maintains 260+ Apify actors and ships updates regularly. Bug reports via the Apify console issues tab get a response within 24 hours. Roadmap requests are welcome โ€” high-demand features ship in the next version.

Home: thenextgennexus.com Full catalog: apify.com/nexgendata