MCP Google Map Server

Name: MCP Google Map Server
Author: cablate

@cablate

About MCP Google Map Server

A powerful Model Context Protocol (MCP) server providing comprehensive Google Maps API integration with LLM processing capabilities.

#ai #dive #mcp #google-map #mcp-server

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "google-maps": {
      "command": "npx",
      "args": [
        "-y",
        "@cablate/mcp-google-map",
        "--stdio"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Tools

Find places near a location by type (restaurant, cafe, hotel, etc.). Supports filtering by radius, rating, and open status.

Free-text place search (e.g., "sushi restaurants in Tokyo"). Supports location bias, rating, open-now filters.

Get full details for a place by its place_id — reviews, phone, website, hours. Optional `maxPhotos` param returns photo URLs.

Convert an address or landmark name into GPS coordinates.

Convert GPS coordinates into a street address.

Calculate travel distances and times between multiple origins and destinations. Driving mode supports `avoid_tolls` and `avoid_highways`.

Get step-by-step navigation between two points with route details. Driving mode supports `avoid_tolls` and `avoid_highways`.

Get elevation (meters above sea level) for geographic coordinates.

Get timezone ID, name, UTC/DST offsets, and local time for coordinates.

Get current weather conditions or forecast — temperature, humidity, wind, UV, precipitation.

Get air quality index, pollutant concentrations, and health recommendations by demographic group.

Generate a map image with markers, paths, or routes — returned inline for the user to see directly.

Geocode up to 50 addresses in one call — returns coordinates for each.

Search for places along a route between two points — ranked by minimal detour time.

Explore what's around a location — searches multiple place types and gets details in one call.

Plan an optimized multi-stop route — uses Routes API waypoint optimization (up to 25 stops) for efficient ordering. Driving mode supports `avoid_tolls` and `avoid_highways`.

Compare places side-by-side — searches, gets details, and optionally calculates distances.

Track a business's local search ranking across a geographic grid — like LocalFalcon. Supports up to 3 keywords for batch scanning. Returns rank at each point, top-3 competitors, and metrics (ARP, ATRP, SoLV).

Overview

What is MCP Google Map Server?

An MCP server providing 18 Google Maps tools (14 atomic + 4 composite) that give AI agents geocoding, routing, place search, directions, elevation, weather, air quality, timezone, and static map capabilities. It integrates with the Google Places API (New) and Routes API, and is designed for developers building location‑aware AI assistants.

How to use MCP Google Map Server?

Run npx @cablate/mcp-google-map --stdio for stdio transport, or npx @cablate/mcp-google-map --port 3000 --apikey "YOUR_API_KEY" for a Streamable HTTP server. A standalone CLI exec mode is also available: npx @cablate/mcp-google-map exec geocode '{"address":"Tokyo Tower"}'. Requires a Google Maps API key (set via environment variable, command‑line flag, or HTTP header).

Key features of MCP Google Map Server

18 tools covering geocoding, directions, place search, weather, air quality, elevation, timezone, and static maps
4 composite tools: explore‑area, plan‑route, compare‑places, local‑rank‑tracker
Three transport modes: stdio, StreamableHTTP, and standalone CLI exec
Tool set filterable via GOOGLE_MAPS_ENABLED_TOOLS environment variable
All tools marked read‑only for safe client auto‑approval
Per‑request API key isolation through HTTP headers

Use cases of MCP Google Map Server

Travel planning with multi‑stop route optimization and place discovery
Local SEO ranking tracking across a geographic grid
Side‑by‑side comparison of places with distance and detail lookups
Batch geocoding up to 50 addresses in one call
Building AI agents that reason about locations, directions, and real‑world data

FAQ from MCP Google Map Server

What tools does it include?

18 tools: maps_search_nearby, maps_search_places, maps_place_details, maps_geocode, maps_reverse_geocode, maps_distance_matrix, maps_directions, maps_elevation, maps_timezone, maps_weather, maps_air_quality, maps_static_map, maps_batch_geocode, maps_search_along_route, plus four composite tools (explore_area, plan_route, compare_places, local_rank_tracker).

How do I get a Google Maps API key?

Create a project in the Google Cloud Console, enable the Places API (New) and Routes API, then generate an API key. Set it via the GOOGLE_MAPS_API_KEY environment variable, the --apikey flag, or the X-Google-Maps-API-Key HTTP header.

Can I run it without an MCP client?

Yes. Use the CLI exec mode: npx @cablate/mcp-google-map exec, followed by the tool name (e.g., geocode) and its parameters as JSON. All 18 tools are available directly.

Is the server read‑only?

All tools are annotated with readOnlyHint: true and destructiveHint: false, meaning MCP clients can auto‑approve requests without user confirmation. No write operations are performed.

How do I limit which tools are exposed?

Set the GOOGLE_MAPS_ENABLED_TOOLS environment variable to a comma‑separated list of tool names (e.g., maps_geocode,maps_directions). Omit it or set to * to expose all 18