# Google Maps

> Geocoding, place search, directions, and travel times from Google Maps.

[Canonical HTML page](https://top-mcps.com/mcp/google-maps) · [server.json](https://top-mcps.com/mcp/google-maps.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "google-maps": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-google-maps"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "${GOOGLE_MAPS_API_KEY}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export GOOGLE_MAPS_API_KEY=AIza_your_api_key
claude mcp add google-maps -- npx -y @modelcontextprotocol/server-google-maps
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "google-maps": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-google-maps"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "${GOOGLE_MAPS_API_KEY}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "google-maps": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-google-maps"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "${GOOGLE_MAPS_API_KEY}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "google-maps": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-google-maps"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "${GOOGLE_MAPS_API_KEY}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "google-maps": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-google-maps"
      ],
      "env": {
        "GOOGLE_MAPS_API_KEY": "${GOOGLE_MAPS_API_KEY}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@modelcontextprotocol/server-google-maps"
          ],
          "env": {
            "GOOGLE_MAPS_API_KEY": "${GOOGLE_MAPS_API_KEY}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.google-maps]
command = "npx"
args = [
  "-y",
  "@modelcontextprotocol/server-google-maps",
]
env = { GOOGLE_MAPS_API_KEY = "${GOOGLE_MAPS_API_KEY}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "google-maps": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@modelcontextprotocol/server-google-maps"
        ]
      },
      "env": {
        "GOOGLE_MAPS_API_KEY": "${GOOGLE_MAPS_API_KEY}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Settings → Connectors → Developer mode`

Enable Developer mode (paid plans) and enter these values in the UI.

```json
{
  "name": "Google Maps",
  "transport": "stdio",
  "command": "npx",
  "args": [
    "-y",
    "@modelcontextprotocol/server-google-maps"
  ],
  "env": {
    "GOOGLE_MAPS_API_KEY": "${GOOGLE_MAPS_API_KEY}"
  }
}
```

## At a glance

- **Maintainer:** Anthropic (modelcontextprotocol)
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** GOOGLE_MAPS_API_KEY
- **Supported clients:** Claude, Cursor, Any MCP-compatible client, Google Cloud accounts
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-04-19
- **GitHub stars:** 84,102 (fetched 2026-04-19T20:32:57.166Z)
- **Score:** 95/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/modelcontextprotocol/servers/tree/main/src/google-maps

## Security & scope

- **Access scope:** network
- **Sandbox:** Read-only calls to the Google Maps Platform API using the key in env.
- **Gotchas:**
  - Google Maps API quotas and billing are per-project — monitor GCP billing if the agent loops.
  - Some endpoints (Places) require separate API enablement in GCP beyond just the key.

## Quick answer

**What it does.** Wraps Google Maps Platform APIs (Geocoding, Places, Directions, Distance Matrix) as MCP tools.

**Best for:**
- Geocoding in agent flows
- Nearby-places search
- Directions and travel times
- Sales/logistics territory queries
- Place detail lookups

**Not for:**
- Map rendering
- Very high-volume production routing

## Recipes

### Find highly-rated places near a landmark

```
Find the 5 highest-rated coffee shops within a 10-minute walk of the Brooklyn Bridge (Manhattan side). Return: name, rating, review count, and walking time from the bridge.
```

_Tested with: Claude Desktop, Cursor_

## Description

The Google Maps MCP gives AI agents geospatial superpowers — geocode addresses, search for places, compute driving/walking directions, pull travel-time matrices, and fetch place details like hours, ratings, and photos.

## Why it matters

Location is core context for travel, logistics, sales, and operations agents. This unlocks all of it via a single standardized interface.

## Key features

- Geocoding (forward + reverse)
- Place search + details
- Directions with multiple modes
- Distance-matrix batch queries
- Photos and ratings metadata

## FAQ

### Do I need a billing account on Google Cloud?

Yes — Maps Platform requires a billing account even for free-tier usage. Google credits the first $200/month, which covers thousands of geocoding calls. Agent-scale use rarely exceeds that.

### Which API scopes does the key need?

Enable Geocoding API, Places API, Directions API, and Distance Matrix API in your Google Cloud project. Restrict the API key to just those services and (ideally) to the IP or referrer where the MCP runs.

### Can it return photos for places?

Yes. The Place Details tool returns photo references, and the MCP exposes a photo fetch helper that pulls the actual image URL for agents to show or caption.

### Does it work for places outside the US?

Yes — Google Maps has global coverage. Data density varies (rural areas outside US/EU have thinner place-level detail), but geocoding, directions, and travel-time queries work worldwide.

## Changelog

- **2026-04-19** — Refreshed install snippets and fact sheet; verified for 2026.
- **2024-12-10** — Initial directory listing.