Google Maps MCP Server Enhanced
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Set to true to enable debug mode for troubleshooting. | |
| GOOGLE_MAPS_API_KEY | Yes | Google Maps API Key with required APIs enabled (Geocoding, Places, Directions, Distance Matrix, Elevation, Maps Static, and Street View Static). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| maps_geocodeC | Convert an address into geographic coordinates |
| maps_reverse_geocodeC | Convert coordinates into an address |
| maps_search_placesC | Search for places using Google Places API |
| maps_place_detailsC | Get detailed information about a specific place |
| maps_distance_matrixB | Calculate travel distance and time for multiple origins and destinations |
| maps_elevationB | Get elevation data for locations on the earth |
| maps_directionsC | Get directions between two points |
| maps_weatherC | Get current weather conditions and forecasts for camping trip planning |
| maps_air_qualityC | Get air quality data for wilderness areas and camping locations |
| maps_solarB | Get solar irradiance data for solar power planning at campsites |
| maps_pollenB | Get pollen and allergy information for outdoor activities |
| maps_routesC | Get enhanced route planning with detailed navigation using Routes API |
| maps_street_viewB | Get Street View images for any location with customizable viewing angle and field of view |
| maps_static_mapB | Get static map images in various styles (satellite, roadmap, terrain, hybrid) with optional markers |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools have distinct purposes, but 'maps_directions' and 'maps_routes' overlap in routing functionality, potentially causing confusion despite different API backends. The environmental tools (air quality, pollen, solar) are well-separated.
All tools follow a consistent 'maps_verb_noun' pattern (e.g., maps_geocode, maps_search_places), with no mixing of styles or irregularities.
14 tools cover a broad range of mapping and environmental features without being excessive; each tool serves a clear purpose within the server's scope.
Covers core mapping, geocoding, places, directions, and environmental data, but lacks place photos, time zone, or nearby search, which are common in Google Maps APIs.