Skip to main content
Glama
Sign In
Google Maps Places Scraper MCP Server

Google Maps Places Scraper MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Google Maps Places Scraper MCP Server

MCP Registry npm version npm downloads license

An MCP server for the Mamba Labs Google Maps Places Scraper actor on Apify. Google Maps place data as rows.

What's Inside

Related MCP server: maps-scrapper

What it does

Takes searches or known place IDs and returns one row per place with phone, website, address, coordinates, categories, rating, review count, hours, and attributes.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-google-maps-places-scraper": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-google-maps-places-scraper"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The search_google_maps_places tool appears.

Prerequisites

Example prompts

  • "Find 20 coffee shops in Austin, TX with their phone and website."

  • "Look up this Google place ID and give me its hours."

Tool

search_google_maps_places. One tool. Example arguments:

{
  "search_terms": [
    "coffee shop in Austin, TX"
  ],
  "max_places_per_search": 5
}

Inputs

Every buyer facing input of the actor. Omitted inputs take the actor's own defaults.

Input

Type

Required

Description

search_terms

array

no

What to search on Google Maps, such as dentist in Austin, TX. One search per entry. Each search returns up to about 120 to 200 places, so split a large area into neighborhoods.

locations

array

no

Optional. Each search term is run once per location, as "term in location". Leave empty when your searches already name the place.

places

array

no

Optional. Look up places you already know: a ChIJ place ID, or a Google Maps place URL. Each costs one place row.

max_places_per_search

number

no

Whole number from 1 to 500. Default 20. Google stops most searches between 120 and 200 places.

only_country

string

no

Optional 2 letter country code, such as DE. Places in other countries are dropped and not charged. A search for Berlin can otherwise return Berlin, New Jersey, on later pages.

dedupe

boolean

no

yes or no. Default yes: a place found twice in a run is returned and charged once.

language

string

no

Language code for names and categories, such as en or de. Default en.

results_country

string

no

2 letter code Google uses to tailor results. Default us. It does not limit results to that country; use only_country for that.

max_charge_usd

number

no

Optional. The run stops before a charge that would pass this amount. Summary rows are always returned.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

Event

Free plan

Bronze

Silver

Gold

place-row, one place

$0.0015

$0.001425

$0.00135

$0.001275

apify-actor-start, per run start

$0.007

$0.007

$0.007

$0.007

Summaries, repeats, and refused input are free. Mamba Labs pays the platform costs of the run, Apify proxy traffic included.

Full actor documentation

apify.com/mambalabs/google-maps-places-scraper

License

MIT. See LICENSE.

Available Tools

1 tool
search_google_maps_placesSearch Google Maps placesA
Read-onlyIdempotent

Search Google Maps or look up known place IDs. Returns one row per place with name, phone, website, address, coordinates, categories, rating, review count, hours, and attributes.

Inputs: dedupe, places, language, locations, +5 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool in the set, there is no possibility of misselection between tools. The tool's purpose (search places and resolve place IDs) is stated clearly enough that an agent will always know when to use it.

    Naming Consistency4/5

    The lone name search_google_maps_places follows a clean verb_noun snake_case convention and is descriptive. There is no second tool to demonstrate a consistent pattern across the set, so it cannot be judged a full 5.

    Tool Count3/5

    A single tool is thin for a scraping server; it bundles search, place-ID lookup, and full detail retrieval into one overloaded endpoint. It is workable but leaves no room for pagination control or separate detail retrieval.

    Completeness3/5

    The tool returns rich per-place data (phone, hours, ratings, attributes), which covers core read workflows, but the surface offers no pagination/bulk iteration, no separate reviews or photos retrieval, and no way to enumerate results beyond one query.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers