Stadia Maps Location API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| time-and-zone-infoA | Get the current time and zone info at any point (geographic coordinates). Output includes includes the standard UTC offset, special offset currently in effect (typically but not always Daylight Saving Time), IANA TZID, and the current timestamp in RFC 28222 format. |
| geocodeA | Look up a street address, POI, or area. Returned geographic information includes coordinates, bounding box, local context (what country, city, etc. is it in).. Additional info may include Wikipedia ID, population, opening hours, website, and more, subject to availability. |
| bulk-geocodeA | Perform multiple address geocoding operations in a single request. Returns results as a JSON list, showing only the first result for each. Using this to geocode POIs is strongly discouraged, as many places with the same name exist; only use this for addresses. Returned geographic information includes coordinates, bounding box, local context (what country, city, etc. is it in). |
| route-overviewB | Get high-level routing information between two or more locations. Includes travel time, distance, and an encoded polyline of the route. The result is JSON. |
| isochroneA | Generate isochrone contours showing areas reachable within specified time or distance constraints from a single location. Returns GeoJSON polygons representing the reachable areas. |
| static-mapB | Generate a PNG map image of an area, optionally including markers and a line (e.g. to draw a route or a boundary) |
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 6 tools
Each tool has a clearly distinct purpose with no overlap: geocode and bulk-geocode handle address/POI lookups (with bulk for batch operations), isochrone generates reachability contours, route-overview provides routing information, static-map creates map images, and time-and-zone-info gives temporal data. The descriptions clearly differentiate their functions, eliminating any ambiguity.
The naming is mostly consistent with a clear snake_case pattern (e.g., bulk-geocode, static-map) and descriptive verb-noun combinations, but 'geocode' deviates slightly as a single word while others use hyphens. This minor inconsistency does not hinder readability or predictability.
With 6 tools, the count is well-scoped for a location API server, covering core functionalities like geocoding, routing, mapping, and time data. Each tool earns its place without redundancy, and the set feels complete for typical location-based tasks.
The tool surface is complete for the location API domain, offering full coverage: geocoding (single and bulk), routing, isochrone analysis, map visualization, and time/zone information. There are no obvious gaps, and agents can handle common workflows like finding places, calculating routes, and displaying maps without dead ends.