google-maps-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR, CRITICAL) | INFO |
| MAX_RESULTS | No | Maximum results to return (1-60) | 20 |
| MAX_RETRIES | No | Maximum retry attempts for failed requests | 3 |
| RETRY_MAX_WAIT | No | Maximum wait between retries (seconds) | 10.0 |
| RETRY_MIN_WAIT | No | Minimum wait between retries (seconds) | 1.0 |
| MAX_RADIUS_METERS | No | Maximum allowed search radius | 50000 |
| GOOGLE_MAPS_API_KEY | Yes | Google Maps Platform API key | |
| DEFAULT_RADIUS_METERS | No | Default search radius in meters | 5000 |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_placesA | Search for nearby places based on location and keywords. Returns place names, addresses, ratings, and other details. |
| get_place_detailsA | Get detailed information about a specific place using its Place ID. Returns address, phone number, website, opening hours, and other details. |
| get_directionsA | Get route directions between origin and destination with real-time traffic data. Returns routes with distance, duration, steps, and traffic information. |
| geocode_addressB | Convert a street address to geographic coordinates (latitude/longitude). |
| reverse_geocodeB | Convert geographic coordinates (latitude/longitude) to a street address. |
| calculate_distance_matrixB | Calculate travel distances and times between multiple origins and destinations. Useful for route optimization and fleet management. |
| snap_to_roadsA | Snap GPS coordinates to the nearest road. Useful for cleaning noisy GPS data from vehicle tracking systems. |
| get_speed_limitsA | Get speed limit data for road segments. Requires place IDs from snap_to_roads. Critical for fleet safety and compliance monitoring. |
| get_traffic_conditionsA | Analyze real-time traffic conditions between origin and destination. Returns duration in traffic, delay estimates, and congestion level. |
| calculate_route_safety_factorsA | Calculate safety assessment for a route. Analyzes traffic congestion, road types, and speed limits to identify risk factors. |
| get_route_elevation_gainA | Calculate elevation gain and retrieve elevation profile for a route. Useful for cycling, hiking, or fuel efficiency analysis. |
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 11 tools
Each tool has a clearly distinct purpose, from geocoding to directions to safety analysis. No two tools overlap in functionality; even geocode and reverse_geocode are complementary opposites.
All tool names follow a consistent verb_noun pattern in snake_case, with verbs like 'calculate', 'get', 'geocode', 'reverse_geocode', 'search', and 'snap'. The naming is predictable and aids agent selection.
With 11 tools covering geocoding, directions, places, traffic, roads, elevation, and safety, the set is well-scoped for Google Maps API capabilities. No unnecessary tools and no obvious missing core operations.
The tool set covers major Google Maps features (geocoding, directions, places, traffic, roads, elevation, distance matrix, safety). Minor gaps exist (e.g., place photos, time zone), but the surface is complete for most common use cases.