Skip to main content
Glama
Sign In
Google Maps MCP Server

Google Maps MCP Server

by Mannycon1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Google Maps MCP Server

An MCP (Model Context Protocol) server that gives Claude and other MCP clients access to the Google Maps Platform: geocoding, place search, place details, directions, distance matrix, and elevation.

Tools

Tool

Description

maps_geocode

Convert an address or place name into coordinates

maps_reverse_geocode

Convert coordinates into a human-readable address

maps_search_places

Free-text place search (restaurants, businesses, landmarks), with optional location bias

maps_place_details

Full details for a place: phone, website, hours, rating, reviews

maps_directions

Turn-by-turn directions (driving, walking, bicycling, transit)

maps_distance_matrix

Travel time and distance between multiple origins and destinations

maps_elevation

Elevation in meters for one or more coordinates

Related MCP server: MCP Google Maps - stdio Edition

Prerequisites

  1. Node.js 18+

  2. A Google Maps API key — create one in the Google Cloud Console:

    • Create (or select) a project

    • Enable these APIs: Geocoding API, Places API, Directions API, Distance Matrix API, Elevation API

    • Create an API key under Credentials

Installation

git clone https://github.com/Mannycon1/Google-Maps-Mcp.git
cd Google-Maps-Mcp
npm install
npm run build

Usage with Claude Desktop

Add this to your claude_desktop_config.json (Claude Desktop → Settings → Developer → Edit Config):

{
  "mcpServers": {
    "google-maps": {
      "command": "node",
      "args": ["/absolute/path/to/Google-Maps-Mcp/dist/index.js"],
      "env": {
        "GOOGLE_MAPS_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Restart Claude Desktop and the Google Maps tools will appear.

Usage with Claude Code

claude mcp add google-maps \
  --env GOOGLE_MAPS_API_KEY=YOUR_API_KEY_HERE \
  -- node /absolute/path/to/Google-Maps-Mcp/dist/index.js

Testing manually

The server speaks JSON-RPC over stdio:

GOOGLE_MAPS_API_KEY=YOUR_KEY node dist/index.js

Then paste an MCP initialize request to interact with it, or use the MCP Inspector:

GOOGLE_MAPS_API_KEY=YOUR_KEY npx @modelcontextprotocol/inspector node dist/index.js

Security notes

  • Never commit your API key. Pass it via the GOOGLE_MAPS_API_KEY environment variable (the .env pattern is gitignored).

  • Consider restricting your API key to only the Maps APIs listed above.

License

MIT

Available Tools

7 tools
maps_directionsA

Get turn-by-turn directions between an origin and destination

Inputs: origin (required), destination (required), mode.

maps_distance_matrixA

Get travel distances and durations between multiple origins and destinations

Inputs: origins (required), destinations (required), mode.

maps_elevationA

Get elevation data (in meters) for one or more geographic coordinates

Inputs: locations (required).

maps_geocodeA

Convert a street address or place name into geographic coordinates (latitude/longitude)

Inputs: address (required).

maps_place_detailsA

Get detailed information about a specific place by its place_id (contact info, hours, reviews, etc.)

Inputs: place_id (required).

maps_reverse_geocodeA

Convert geographic coordinates (latitude/longitude) into a human-readable address

Inputs: latitude (required), longitude (required).

maps_search_placesA

Search for places (restaurants, businesses, landmarks, etc.) using a free-text query, optionally biased to a location

Inputs: query (required), radius, latitude, longitude.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct Maps operation: address-to-coordinates, coordinates-to-address, place lookup by ID, free-text place search, directions, distance matrix, and elevation. The only mild overlap is between geocode and search_places, but their inputs and outputs are clearly different enough to avoid confusion.

    Naming Consistency5/5

    All tools follow a consistent maps_ prefix with snake_case action-based naming (maps_geocode, maps_search_places, maps_distance_matrix). The naming pattern is uniform, predictable, and instantly communicates the tool's purpose.

    Tool Count5/5

    Seven tools is a well-scoped size for a Google Maps MCP server. Each tool covers a major Maps API use case without unnecessary redundancy or feature bloat.

    Completeness4/5

    The core map workflows are covered: location lookup, place search and details, routing, distance calculation, and elevation. Minor gaps like place autocomplete or timezone lookups exist, but they do not create dead ends for most common use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers