Log inSubmit server
MCP Google Map logo

MCP Google Map

by cablate

Google Maps MCP server with 18 read-only tools for places, geocoding, routing, environmental data, maps, and local SEO.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Google Map

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "cablate-mcp-google-map": {
      "command": "npx",
      "args": [
        "-y",
        "@cablate/mcp-google-map"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "YOUR_VALUE_HERE",
        "GOOGLE_MAPS_ENABLED_TOOLS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

cablate/mcp-google-map connects AI agents to Google Maps Platform through 18 read-only tools for place discovery, geocoding, routing, weather, air quality, maps, and local search analysis. It supports local stdio connections and Streamable HTTP deployments, plus a stateless CLI for scripts and Agent Skills. Composite tools can explore areas, compare places, find route stops, optimize up to 25 waypoints, and track rankings across a geographic grid. Reach for it when an agent needs location data and multi-step travel or local SEO workflows backed by Google Maps APIs.

Use cases

  • Find restaurants, hotels, cafes, and other nearby places
  • Plan multi-stop routes with optimized waypoint ordering
  • Compare candidate places with travel distances and details
  • Enrich address lists with batch geocoding
  • Measure local search rankings across a geographic grid

Key features

  • 18 read-only Google Maps tools
  • Stdio and Streamable HTTP transports
  • Stateless CLI execution
  • Route planning for up to 25 stops
  • Batch geocoding for up to 50 addresses
  • Local ranking and competitor tracking

Tools18

What MCP Google Map lets your agent do. Expand a tool for its parameters.

Self-reported~543 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

20/20 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @cablate/mcp-google-map (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars484Stargazers on the source repository.
npm downloads5.5kPackage downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Tools exposed18Callable tools this server registers over MCP.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Google Map works

What cablate/mcp-google-map does

cablate/mcp-google-map exposes Google Maps Platform capabilities to AI agents through MCP, a standalone command-line interface, and three Agent Skills. Its catalog contains 18 read-only tools covering place discovery, location conversion, route planning, environmental context, map images, and local search visibility.

Place tools support free-text and nearby searches, place details, area exploration, side-by-side comparisons, and searches for stops along a route. Location and routing tools convert addresses and coordinates, calculate distance and travel time, return turn-by-turn routes, process batches of up to 50 addresses, and optimize routes with up to 25 stops. Additional tools retrieve elevation, timezone, weather, air quality, and static map images.

The local SEO tool scans a geographic grid for a business and up to three keywords, returning rankings, competitors, and metrics such as ARP, ATRP, and SoLV.

How it works

The server uses a Google Maps Platform API key and can run as a local stdio process or as a self-hosted Streamable HTTP service at /mcp. Stdio clients start the process locally; HTTP deployments can serve shared, containerized, LAN, or remote sessions. Request headers can carry separate API keys for session isolation in multi-tenant HTTP setups.

Every CLI invocation is stateless and returns structured JSON on success. The CLI offers short command names such as geocode, search-places, and directions, while MCP clients receive the full tool names. Agent Skills provide workflow guidance for general map research, travel planning, and local SEO, and can call the CLI without starting an MCP server.

All tools are marked read-only and non-destructive. Google API requests may incur billing, and applications using Places reviews, photos, or generated summaries must follow Google’s attribution and storage requirements.

Setup and configuration

Node.js 22 or newer and a Google Maps Platform API key are required. The Google Cloud project must have billing enabled, and each selected workflow needs its corresponding API enabled. Common place and route workflows use Places API (New), Routes API, and often Geocoding API.

For stdio, set GOOGLE_MAPS_API_KEY in the MCP client configuration and launch the package with --stdio. For HTTP, start the process with a host, port, and API key, then point the client at /mcp. The GOOGLE_MAPS_ENABLED_TOOLS variable accepts a comma-separated allowlist, which can reduce the tools exposed to an MCP client; omitting it or using * exposes the full catalog.

The doctor command checks the local Node.js, package, and API-key setup without making a live Google request. Adding --live performs billable checks against Geocoding, Places, and Routes.

Tools and capabilities

  • Search nearby places by type, radius, rating, and open status.
  • Search places with free-text queries and location bias.
  • Retrieve place details including reviews, contact information, hours, and optional photo URLs.
  • Geocode addresses individually or in batches of up to 50, and reverse-geocode coordinates.
  • Calculate distance matrices and detailed directions, including toll and highway avoidance for driving routes.
  • Search along routes, compare places, explore multiple categories, and optimize routes with up to 25 stops.
  • Retrieve elevation, timezone, current weather or forecasts, air quality, and inline static map images.
  • Measure local rankings across a geographic grid, including competitors and visibility metrics.

Limitations and notes

The tools provide data and planning inputs rather than guarantees about safety, accessibility, opening status, or ranking results. API availability and billing depend on the Google Cloud APIs enabled for the project. Static map output is returned as an image for the user to view directly. Applications that display Google Places reviews or photos must observe the applicable attribution and storage rules.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Google Map

cablate/mcp-google-map is an MCP server that connects AI agents to Google Maps Platform through 18 read-only tools. Its main tools search and inspect places, geocode addresses, calculate routes and distances, retrieve weather and air quality, generate static maps, optimize multi-stop trips, and track local search rankings.

Install and run it with Node.js 22 or newer using the npm package, then provide a Google Maps Platform API key. For MCP clients, launch `npx -y @cablate/mcp-google-map --stdio`; for HTTP, start it with a host, port, and API key. The package also supports Codex and Claude Code plugin installation.

Configure Claude Desktop to start the package over stdio and set `GOOGLE_MAPS_API_KEY` in the server environment. You can optionally set `GOOGLE_MAPS_ENABLED_TOOLS` to a comma-separated list such as `maps_geocode,maps_directions,maps_search_places` to expose only selected tools.

Yes, cablate/mcp-google-map works with Cursor through its stdio MCP configuration. Cursor starts the local process, while the server reads `GOOGLE_MAPS_API_KEY` from the configured environment. A Streamable HTTP endpoint is also available for clients that connect to remote MCP services.

The required APIs depend on the tools you use. Common place and routing workflows require Places API (New) and Routes API, while geocoding workflows often require Geocoding API. The Google Cloud project must have billing enabled, and live requests may be billable.

Related MCP servers

All in Location Services All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Google Map AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/cablate-mcp-google-map?style=directory)](https://allmcps.com/mcp/cablate-mcp-google-map)
HTML Embed
<a href="https://allmcps.com/mcp/cablate-mcp-google-map"><img src="https://allmcps.com/api/badge/cablate-mcp-google-map?style=directory" alt="MCP Google Map on AllMCPs" /></a>