MCP Google Maps
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL | No | Cache time-to-live in seconds | 3600 |
| DEFAULT_REGION | No | Default region for responses | US |
| ENABLE_CACHING | No | Enable caching of responses | true |
| DEFAULT_LANGUAGE | No | Default language for responses | en |
| GOOGLE_MAPS_API_KEY | Yes | Your Google Maps API key | |
| MAX_REQUESTS_PER_DAY | No | Maximum number of requests per day | 100000 |
| MAX_REQUESTS_PER_SECOND | No | Maximum number of requests per second | 50 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_nearbyC | Search for places near a specific location |
| get_place_detailsB | Get detailed information about a specific place |
| get_geocodeC | Convert an address to coordinates |
| get_reverse_geocodeB | Convert coordinates to an address |
| get_distance_matrixB | Calculate distance and time between multiple origins and destinations |
| get_directionsC | Get directions between two locations |
| get_elevationC | Get elevation data for locations |
| get_map_with_directionsC | Generate a static map with directions overlay |
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 8 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, get_directions is for routing, get_distance_matrix is for multi-point calculations, and get_geocode vs get_reverse_geocode handle opposite conversions. The descriptions reinforce these unique functions, making tool selection straightforward.
All tools follow a consistent verb_noun pattern with 'get_' or 'search_' prefixes, such as get_directions, get_geocode, and search_nearby. This uniformity enhances readability and predictability, allowing agents to easily understand the tool set's structure.
With 8 tools, the count is well-scoped for a Google Maps server, covering core functionalities like directions, geocoding, place search, and maps. Each tool earns its place by addressing a specific aspect of location-based services without redundancy or bloat.
The tool set provides complete coverage for the Google Maps domain, including routing (directions, distance matrix), geospatial conversions (geocode, reverse geocode), place information (details, nearby search), and visualization (map with directions). No obvious gaps exist, enabling agents to handle typical mapping workflows effectively.