Google Maps MCP Server: Setup Guide, Use Cases & Limitations

What Is Google Maps MCP Server?

Google Maps MCP Server exposes Google Maps Platform capabilities — geocoding, place search, directions, and distance matrix calculations — as MCP tools that Claude can call directly. It is maintained by the Model Context Protocol team as part of the official modelcontextprotocol/servers monorepo.

Quick Facts

What You Can Do With It

• Geocoding: Convert a street address or place name into geographic coordinates (latitude/longitude) and reverse-geocode coordinates back to a human-readable address.
• Place search: Query the Places API to find businesses, landmarks, or points of interest by name or category near a given location.
• Place details: Retrieve structured information about a specific place — address, phone number, opening hours, and ratings — using a place ID.
• Directions: Get step-by-step routing between an origin and destination, including support for travel mode (driving, walking, transit, cycling).
• Distance matrix: Calculate travel time and distance between multiple origins and destinations in a single request, useful for comparing route options.

How to Set It Up

Prerequisites: You need a Google Maps Platform API key with the relevant APIs enabled (Geocoding, Places, Directions, Distance Matrix). Create one at console.cloud.google.com.

Claude Desktop — add the following to claude_desktop_config.json (typically at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "google-maps": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-google-maps"],
      "env": {
        "GOOGLE_MAPS_API_KEY": "your_api_key_here"
      }
    }
  }
}
**Claude Code** — run the following CLI command to register the server:

```bash
claude mcp add google-maps \
  -e GOOGLE_MAPS_API_KEY=your_api_key_here \
  -- npx -y @modelcontextprotocol/server-google-maps

In both cases the API key is passed via the GOOGLE_MAPS_API_KEY environment variable. Restart the client after saving the configuration.

Works Best With

This server is documented as compatible with Claude Desktop and Claude Code. Both clients support the full MCP tool-calling flow required to invoke geocoding, directions, and places queries interactively. Claude Code is the better fit for programmatic workflows — scripted location lookups, batch geocoding in a development context — while Claude Desktop suits conversational, ad-hoc mapping queries.

Known Limitations

• API key required: The server will not start without a valid GOOGLE_MAPS_API_KEY. Each Google Maps Platform API (Geocoding, Places, Directions, Distance Matrix) must be individually enabled in your Google Cloud project.
• Billing: Google Maps Platform is a paid service after free-tier credits are exhausted. High-volume use — especially distance matrix calls with many origins/destinations — can accumulate costs quickly.
• Rate limits: Requests are subject to Google Maps Platform quotas (queries per second and per day). The server does not implement its own retry or backoff logic, so bursts may result in errors that surface directly to the model.
• No map rendering: The server returns data only — coordinates, text directions, distance values. It cannot generate or display visual maps.
• Static data: Real-time traffic accuracy depends on the underlying API response; the server adds no caching layer.

Community Resources

• GitHub repository & issue tracker — file bugs or check existing issues against the google-maps source directory
• MCP Discord server — #servers channel is the most active place for troubleshooting MCP server configuration
• r/ClaudeAI on Reddit — search “Google Maps MCP” for community configuration threads