I built a Google Maps MCP server with 15 tools — the official one is deprecated and only had 7
The original @modelcontextprotocol/server-google-maps from Anthropic is unmaintained and uses the legacy Places API. I built a replacement that covers significantly more of the Google Maps Platform.
15 tools across three categories:
Places: places_geocode, places_details, places_text_search, places_nearby_search, places_autocomplete, places_photos, places_address_validation, places_timezone
Routes: routes_compute, routes_matrix, routes_optimize (waypoint ordering)
Maps: maps_static_map, maps_embed_url, maps_street_view, maps_elevation
What makes it different from other community servers:
- Uses the new Places API — no legacy deprecation warnings
routes_optimizefor multi-stop route ordering (rare in MCP servers)places_address_validationandplaces_timezone— most servers skip these- HTTP Streamable transport with stateful sessions
- Security hardened: constant-time token comparison, session TTL, input size limits
Install:
GOOGLE_MAPS_API_KEY=your_key MCP_AUTH_TOKEN=your_token npx mcp-server-google-maps
Claude Desktop config:
{
"mcpServers": {
"google-maps": {
"command": "npx",
"args": ["mcp-remote", "http://localhost:3003/mcp", "--header", "X-Api-Key: your_token"]
}
}
}
GitHub: https://github.com/apurvaumredkar/google-maps-mcp
npm: https://www.npmjs.com/package/mcp-server-google-maps
Happy to answer questions. Also open to PRs if there are APIs you'd like added.
Posted Mar 8, 2026, 8:02 PM UTC