Google Maps Places Scraper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token, available from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_google_maps_placesA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.