Google Maps Geocoding MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_MAPS_API_KEY | Yes | Your Google Maps API key from the Google Cloud Console |
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 |
|---|---|
| geocode_forwardB | Convert an address to geographic coordinates (latitude/longitude) using Google Maps Geocoding API. |
| geocode_reverseB | Convert geographic coordinates (latitude/longitude) to a human-readable address using Google Maps Geocoding API. |
| geocode_placeC | Convert a Google Place ID to a human-readable address using Google Maps Geocoding API. |
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 3 tools
Each tool has a clearly distinct purpose: geocode_forward handles addresses to coordinates, geocode_place converts Place IDs to addresses, and geocode_reverse does coordinates to addresses. There is no overlap or ambiguity between these three operations.
All tool names follow a consistent 'geocode_' prefix with descriptive suffixes (forward, place, reverse), using snake_case uniformly. This pattern is predictable and enhances readability.
With 3 tools, the server is well-scoped for geocoding operations, covering the essential forward, reverse, and Place ID conversions. Each tool earns its place without being excessive or insufficient for the domain.
The tool set provides complete coverage for the Google Maps Geocoding domain, including forward geocoding, reverse geocoding, and Place ID resolution. There are no obvious gaps, as these are the core operations offered by the API.