Google Maps MCP Server
Provides tools for geocoding, reverse geocoding, place searching, retrieving place details, calculating distances between points, obtaining elevation data, and generating directions with route information using the Google Maps API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Google Maps MCP Server how far is it from Central Park to Times Square by walking?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Google Maps MCP Server
MCP Server for the Google Maps API.
Tools
maps_geocodeConvert address to coordinates
Input:
address(string)Returns: location, formatted_address, place_id
maps_reverse_geocodeConvert coordinates to address
Inputs:
latitude(number)longitude(number)
Returns: formatted_address, place_id, address_components
maps_search_placesSearch for places using text query
Inputs:
query(string)location(optional): { latitude: number, longitude: number }radius(optional): number (meters, max 50000)
Returns: array of places with names, addresses, locations
maps_place_detailsGet detailed information about a place
Input:
place_id(string)Returns: name, address, contact info, ratings, reviews, opening hours
maps_distance_matrixCalculate distances and times between points
Inputs:
origins(string[])destinations(string[])mode(optional): "driving" | "walking" | "bicycling" | "transit"
Returns: distances and durations matrix
maps_elevationGet elevation data for locations
Input:
locations(array of {latitude, longitude})Returns: elevation data for each point
maps_directionsGet directions between points
Inputs:
origin(string)destination(string)mode(optional): "driving" | "walking" | "bicycling" | "transit"
Returns: route details with steps, distance, duration
Related MCP server: MCP Google Maps
Setup
API Key
Get a Google Maps API key by following the instructions here.
Usage with Claude Desktop
Add the following to your claude_desktop_config.json:
Docker
{
"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>"
}
}
}
}NPX
{
"mcpServers": {
"google-maps": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-google-maps"
],
"env": {
"GOOGLE_MAPS_API_KEY": "<YOUR_API_KEY>"
}
}
}
}Build
Docker build:
docker build -t mcp/google-maps -f src/google-maps/Dockerfile .License
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Available Tools
4 toolsadd_postC
Adds a simple text post.
Inputs: content (required).
delete_postC
Deletes a post by ID.
Inputs: id (required).
get_postsC
Retrieves all posts.
Inputs: no named parameters.
get_weatherC
Gets the current weather.
Inputs: location (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Three tools (add_post, delete_post, get_posts) clearly relate to a posts/CRUD domain, while get_weather is unrelated to posts and creates a domain mismatch. Within the posts tools, there is good disambiguation (add, delete, get), but the inclusion of weather introduces significant ambiguity about the server's purpose and tool boundaries.
The naming follows a consistent verb_noun pattern (add_post, delete_post, get_posts, get_weather) with clear actions and objects. All tools use snake_case uniformly, making them readable and predictable, though the weather tool's domain deviation slightly affects overall consistency.
With 4 tools, the count is reasonable, but it feels thin for a 'Google Maps MCP Server' as it lacks core mapping functionalities (e.g., geocoding, directions, places search). The tools present cover a basic posts system and weather, which is mismatched with the server name, making the scope unclear and borderline inappropriate.
For a posts domain, the tools provide basic CRUD (add, delete, get) but lack update functionality, creating a minor gap. More critically, for a Google Maps server, there are no mapping-related tools (e.g., search_places, get_directions), resulting in significant gaps that will cause agent failures in handling mapping tasks.
Maintenance
Related MCP Connectors
Google Maps MCP Pack — geocoding, places, directions, distance matrix, elevation. Uses Google Maps…
Hosted MCP for live place search, geocoding & turn-by-turn routes. No Maps API key to manage.
Google Maps routes, ETAs, and turn-by-turn steps via the Apify Directions API, hosted MCP.
Live Google Maps business search, review, and photo data for AI agents over MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceIntegrates with Google Places API to allow searching, retrieving details, and finding nearby places through an MCP server interface.ISC
- AlicenseAqualityBmaintenanceProvides access to Google Maps API functionality including places search, geocoding, directions, distance matrix, elevation data, and static map generation through the MCP interface.81MIT
- AlicenseNot gradedqualityDmaintenanceProvides MCP tools for Google Maps services including directions, geocoding, distance matrix, and places search.13Apache 2.0
- AlicenseBqualityDmaintenanceProvides comprehensive access to Google Maps Platform APIs through MCP, enabling geocoding, places search, routing, and geospatial operations.15108 npm3MIT