- Home
- MCP servers
- Google Maps
Google Maps
- javascript
0
GitHub Stars
javascript
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
You deploy this MCP server to access Google Maps capabilities from your apps. It exposes a set of endpoints that let you geocode addresses, reverse geocode coordinates, search places, fetch place details, compute distances and routes, and retrieve elevation data. Use it from your MCP client to integrate maps data and directions into your workflows without embedding API keys or client logic in your main application.
How to use
To start querying Google Maps data through MCP, first ensure your MCP client is configured to reach one of the available server runtimes shown below. You can run the server locally via a container or via NPX, then call its endpoints for geocoding, reverse geocoding, place search, and more. Each tool corresponds to a specific function you can invoke from your client.
Available tools include geocoding an address, converting coordinates back to an address, searching for places with optional location and radius, getting place details by place_id, computing distance matrices, retrieving elevation data for locations, and obtaining driving or walking directions. Use these helpers to build features like location search, route planning, and location-based content enrichment in your app.
How to install
Prerequisites you need before installing include Node.js for npm/npx workflows or Docker if you prefer containerized runs.
Install by choosing one of the provided runtimes. The following options are explicitly shown for running the MCP server.
Option 1: Run via Docker Use the Docker command to start a container that serves the Google Maps MCP endpoints. You must supply your Google Maps API key as an environment variable.
{
"mcpServers": {
"google_maps": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GOOGLE_MAPS_API_KEY",
"mcp/google-maps"
],
"env": {
"GOOGLE_MAPS_API_KEY": "<YOUR_API_KEY>"
}
}
}
}
Option 2: Run via NPX
Use NPX to run the server directly without building a container image. Provide your API key as an environment variable.
{
"mcpServers": {
"google_maps": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-google-maps"
],
"env": {
"GOOGLE_MAPS_API_KEY": "<YOUR_API_KEY>"
}
}
}
}
Available tools
maps_geocode
Convert an address to geographic coordinates. Input: address string. Output includes location, formatted_address, and place_id.
maps_reverse_geocode
Convert latitude and longitude to a human-readable address. Inputs: latitude, longitude. Output includes formatted_address, place_id, and address_components.
maps_search_places
Search for places using a text query. Inputs: query string, optional location with latitude/longitude, optional radius in meters (max 50000). Output is an array of places with names, addresses, and locations.
maps_place_details
Get detailed information about a place. Input: place_id string. Output includes name, address, contact info, ratings, reviews, and opening hours.
maps_distance_matrix
Calculate distances and times between points. Inputs: origins array, destinations array, optional mode (driving, walking, bicycling, transit). Output is a distances and durations matrix.
maps_elevation
Get elevation data for locations. Input: locations as an array of coordinates. Output provides elevation data for each point.
maps_directions
Get directions between origin and destination. Inputs: origin string, destination string, optional mode (driving, walking, bicycling, transit). Output includes route details with steps, distance, and duration.