MCP.so
Sign In
Servers

MCP Google Map Server

@cablate

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

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

Tags

More from Media & Design