# HasData Google Maps [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/HasData/google-maps-mcp  
**GitHub Stars:** 6  
**npm Downloads (last month):** 1159  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/hasdata-google-maps

## Description
Google Maps places, reviews, contributor history, photos and posts as JSON. No Google Cloud.

## Tools
Capabilities this server exposes over MCP:

- **hasdata_google_maps_contributor_reviews_getMapReviews** — Per-review rating, text, date, place name, place address, placeId, photos, and owner responses. 10 credits a call
- **hasdata_google_maps_photos_getMapPhotos** — Each photo with image URL, thumbnail, upload date, uploader, and photoId. 10 credits a call
- **hasdata_google_maps_place_getPlaceDetails** — Name, address, coordinates, phone, website, categories, hours, rating, review count, price level, photos, popular times, attributes/amenities, plus_code, and map URL. 10 credits a call
- **hasdata_google_maps_posts_getMapPosts** — Per-post title, description, image, posted_at, link, and source/business name. 10 credits a call
- **hasdata_google_maps_reviews_getMapReviews** — Per-review author name and profile link, star rating, text, published/relative date, likes count, owner response, attached photos, and local-guide flag. 10 credits a call
- **hasdata_google_maps_search_performMapSearch** — The local pack list with placeId, name, address, coordinates, rating, review count, price level, categories, phone, website, hours, and thumbnail. 10 credits a call

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "hasdata-google-maps": {
    "command": "npx",
    "args": ["-y","@hasdata/google-maps-mcp"],
    "env": {
      "HASDATA_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `HASDATA_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What HasData Google Maps MCP server does

The HasData Google Maps MCP server exposes read-only access to Google Maps information through MCP. Its six tools cover local search, individual place records, customer reviews, image collections, business posts, and the review history associated with a contributor.

Search results can include a place ID and data ID alongside names, addresses, coordinates, ratings, review counts, price levels, categories, contact details, hours, and thumbnails. A place-details request adds fields such as phone number, website, photos, popular times, amenities, plus code, and map URL.

Review tools return structured records rather than requiring an agent to interpret a page. Depending on the request, records include author information, profile links, ratings, text, dates, likes, owner replies, attached photos, and local-guide status. Contributor history provides each reviewer's rating, text, date, place information, photos, and owner responses. Photo and post tools return media or publication metadata, including image URLs, uploaders, titles, descriptions, links, and source business names.

## How it works

The hosted service is available at `https://mcp.hasdata.com/mcp?apis=google_maps` using streamable HTTP. Requests authenticate with the `x-api-key` header. An MCP client handles tool invocation and presents the returned data to the model as structured results.

A typical workflow starts with a map search, then reuses the returned place or data identifier for details, reviews, photos, or posts. Review results also provide a contributor identifier, allowing a follow-up request for that person's reviewed places without a separate lookup step. Direct callers should note that the response contains a text block whose contents are JSON; the scraped payload is nested under its `json` field.

The HasData Google Maps MCP server is remote, so the hosted option does not require a container, local service, Google Cloud project, or Google Maps API key. It uses HasData credits, and the repository describes a free monthly allocation with no card required.

## Setup and configuration

Create a HasData API key from the HasData dashboard, then configure the remote URL and `x-api-key` header in an MCP client. The README provides configurations for Claude Code, Cursor, Windsurf, Cline, VS Code, and Gemini CLI. OAuth-capable clients can add the URL as a connector instead of placing the key in a configuration file.

Claude Desktop's documented path uses a local stdio launcher because its configuration loads local servers. The npm package `@hasdata/google-maps-mcp` can be run with `npx`, and the PyPI package `hasdata-google-maps-mcp` can be launched with `uvx`; both read `HASDATA_API_KEY` from the environment.

## Tools and capabilities

- `hasdata_google_maps_search_performMapSearch`: Finds local-pack places and returns identifying, contact, rating, category, hours, and thumbnail fields.
- `hasdata_google_maps_place_getPlaceDetails`: Retrieves expanded information for one place.
- `hasdata_google_maps_reviews_getMapReviews`: Retrieves reviews and related author, response, photo, and local-guide data.
- `hasdata_google_maps_contributor_reviews_getMapReviews`: Lists a contributor's reviewed places and per-review details.
- `hasdata_google_maps_photos_getMapPhotos`: Returns photo URLs, thumbnails, upload dates, uploaders, and photo IDs.
- `hasdata_google_maps_posts_getMapPosts`: Returns business post text, images, dates, links, and source names.

All six tools are read-only. Calls consume HasData credits; the exact charge depends on the tool and should be checked against the current service terms rather than assumed from examples.

## Limitations and notes

This server reads Google Maps data but does not provide write operations. It requires an MCP client that supports streamable HTTP and custom headers for direct remote use. Clients limited to stdio need one of the provided launchers or another compatible local bridge.

Returned values can change as places receive new reviews or other updates. The server does not eliminate the need to manage API-key secrecy or monitor credit usage. For integrations that call the endpoint without a chat client, the caller must parse the JSON contained in the returned text block.

_Full upstream README: https://allmcps.com/mcp/hasdata-google-maps/readme_