cablate/mcp-google-map

npx @cablate/mcp-google-map --stdio (MCP server; requires GOOGLE_MAPS_API_KEY)
Prerequisite: enable Places API (New) and Routes API in Google Cloud Console before using place/routing tools
HTTP server: npx @cablate/mcp-google-map --port 3000 --apikey "YOUR_API_KEY"

Usage

• •MCP config: {"mcpServers":{"google-maps":{"command":"npx","args":["-y","@cablate/mcp-google-map","--stdio"],"env":{"GOOGLE_MAPS_API_KEY":"..."}}}
• •Limit context: set GOOGLE_MAPS_ENABLED_TOOLS to a comma list (e.g. maps_geocode,maps_directions,maps_search_places); omit or * for all 18
• •Exec CLI without a server: npx @cablate/mcp-google-map exec geocode '{"address":"Tokyo Tower"}'
• •Batch geocode from file: npx @cablate/mcp-google-map batch-geocode -i addresses.txt -o results.json

Key features

• ✓14 atomic tools: search_nearby, search_places, place_details, geocode/reverse_geocode, distance_matrix, directions, elevation, timezone, weather, air_quality, static_map, batch_geocode (up to 50), search_along_route
• ✓4 composite tools: explore_area, plan_route (waypoint optimization up to 25 stops), compare_places, local_rank_tracker (local SEO grid ranking like LocalFalcon)
• ✓Built-in agent skill (skills/google-maps/) teaches chaining of geo tools
• ✓All tools annotated readOnlyHint:true / destructiveHint:false so MCP clients can auto-approve
• ✓3 modes: stdio, Streamable HTTP, standalone exec CLI; per-request API-key isolation for HTTP multi-session deployments

Best for

AI-powered travel planning, logistics route optimization, real-estate/neighborhood analysis, and local SEO audits

Caveats

• ⚠Requires Google Cloud API keys and enabling the (paid) Places API (New) and Routes API
• ⚠Some tools (weather, air quality) are covered by Google Grounding Lite but the full toolset is not
• ⚠HTTP mode binds all interfaces when --host 0.0.0.0 — use API-key isolation / DNS-rebinding protection for remote access