MCP.so
Sign In

MCP Google Map Server

@cablate

About MCP Google Map Server

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

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

18

Find places near a specific location by type (e.g., restaurants, cafes, hotels). Use when the user wants to discover what's around a given address or coordinates, such as 'find coffee shops near Times Square' or 'what hotels are near the airport'. Supports filtering by place type, search radius, minimum rating, and whether currently open.

Get comprehensive details for a specific place using its Google Maps place_id. Use after search_nearby or maps_search_places to get full information including reviews, phone number, website, and opening hours. Set maxPhotos (1-10) to include photo URLs — omit or set to 0 for no photos (saves tokens).

Convert an address, city name, or landmark into GPS coordinates (latitude/longitude). Use when you need coordinates for a location described in text — for example, to provide a center point for search_nearby or a starting point for maps_directions.

Convert GPS coordinates (latitude/longitude) into a human-readable street address. Use when you have coordinates from another tool's output or a user's shared location and need the actual address.

Calculate travel distances and durations between multiple origins and destinations in a single request. Use for comparing travel options — e.g., 'which hotel is closest to the office?' or batch distance calculations. Supports driving, walking, bicycling, and transit modes.

Get step-by-step navigation directions between two points with route details. Use when the user asks 'how do I get from A to B?' and needs the route summary, total distance, estimated travel time, or turn-by-turn instructions. Supports departure/arrival times and multiple travel modes.

Get elevation (meters above sea level) for geographic coordinates. Use when the user asks 'how high is this place', 'is this area flood-prone', or needs altitude for hiking/cycling route profiles. Also useful for real estate risk assessment — low elevation near water suggests flood risk.

Search for places using a free-text query like 'sushi restaurants in Tokyo' or 'best coffee shops near Central Park'. More flexible than search_nearby — supports natural language queries, optional location bias, rating filters, and open-now filtering. Use when the user describes what they're looking for in words rather than by type and coordinates.

Get the timezone and current local time for a location. Use when the user asks 'what time is it in Tokyo', needs to coordinate a meeting across timezones, or is planning travel across timezone boundaries. Returns timezone ID, UTC/DST offsets, and computed local time.

Get weather for a location — current conditions, daily forecast (10 days), or hourly forecast (240 hours). Use when the user asks 'what's the weather in Paris', is planning outdoor activities, or needs to pack for a trip. Coverage: most regions supported, but China, Japan, South Korea, Cuba, Iran, North Korea, Syria are unavailable.

Explore what's around a location in one call — searches multiple place types, gets details for the top results, and returns a categorized summary. Use when the user asks 'what's around here', 'explore the area near my hotel', or needs a quick overview of a neighborhood. Replaces the manual chain of geocode → search-nearby → place-details. For trip planning: use search_places first to get geographically spread anchor points, then call this tool around each anchor (e.g. 'Gion, Kyoto') — never pass just the city name, as it clusters all results in one area. After results, call static_map to visualize.

Plan an optimized multi-stop route in one call — geocodes all stops, uses Routes API waypoint optimization (up to 25 intermediate stops) to find the most efficient visit order, and returns directions for each leg. Use when the user says 'visit these 5 places efficiently', 'plan a route through A, B, C', or needs a multi-stop itinerary. Replaces the manual chain of geocode → distance-matrix → directions. For multi-day trips: create one plan_route call per day with stops that follow a geographic arc (e.g. east→west) rather than mixing distant areas. After results, call static_map to visualize the route.

Compare multiple places side-by-side in one call — searches by query, gets details for each result, and optionally calculates distance from your location. Use when the user asks 'which restaurant should I pick', 'compare these hotels', or needs a decision table. Replaces the manual chain of search-places → place-details → distance-matrix.

Get air quality for a location — AQI index, pollutant concentrations, and health recommendations by demographic group (elderly, children, athletes, pregnant women, etc.). Use when the user asks 'is the air safe', 'should I wear a mask', 'good for outdoor exercise', or is planning travel for someone with respiratory/heart conditions. Coverage: global including Japan (unlike weather). Returns both universal AQI and local index (EPA for US, AEROS for Japan, etc.).

Generate a map image with markers, paths, or routes — returned as an inline image the user can see directly in chat. PROACTIVELY call this tool after explore_area, plan_route, search_nearby, or directions to visualize results on a map — don't wait for the user to ask. Use markers from search results and path from route data. Supports roadmap, satellite, terrain, and hybrid views. Max 640x640 pixels.

Geocode multiple addresses in one call — up to 50 addresses, returns coordinates for each. Use when the user provides a list of addresses and needs all their coordinates, e.g. 'geocode these 10 offices' or 'get coordinates for all these restaurants'. For more than 50, use the CLI batch-geocode command instead.

Search for places along a route between two points — restaurants, cafes, gas stations, etc. ranked by minimal detour time. Use for trip planning to find meals, rest stops, or attractions between landmarks without backtracking. Internally computes the route, then searches along it. Essential for building itineraries where stops should feel 'on the way' rather than 'detour to'.

Track a business's local search ranking across a geographic grid (like LocalFalcon). Searches the same keyword(s) from multiple coordinates around a center point to see how rank varies by location. Supports up to 3 keywords for batch scanning. Returns rank at each grid point, top-3 competitors per point, and summary metrics (ARP, ATRP, SoLV). Useful for local SEO analysis.

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

Frequently asked questions

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

Comments

More Media & Design MCP servers