Hosted MCP for live place search, geocoding & turn-by-turn routes. No Maps API key to manage.
Scored across 5 tools
Each tool has a clearly distinct purpose: routing (directions), address/coordinate conversion (geocode), single-place lookup by ID (places_details), radius search with existing coordinates (places_nearby), and free-text discovery (places_search_text). The descriptions explicitly cross-reference each other to resolve the one plausible overlap (nearby vs. search_text).
The three place_* tools follow a clean prefix_noun convention, and all names are lowercase snake_case. However, directions and geocode stand apart as bare verbs rather than following a uniform pattern, a minor deviation but still readable and predictable.
Five tools is well-scoped for a maps/location server, and each tool covers a genuinely distinct capability (routing, geocoding, text search, nearby search, place details). No tool feels redundant or padded.
Covers the core lifecycle: forward/reverse geocoding, routing, place discovery (text and nearby), and place details with phone/website/hours. Minor gaps exist (no autocomplete/predictions, distance matrix, or time zone/elevation), but agents can work around these for most workflows.
Compute a route from origin to destination by DRIVE, WALK, BICYCLE, TRANSIT, or TWO_WHEELER. Use when the user asks how to get somewhere, how far it is, or how long it takes. Origin and destination may be an address string, "lat,lng", or an object with place_id. Returns total duration and distance, an encoded polyline, and per-leg turn-by-turn steps (maneuver, instruction text, distance, duration, start/end lat/lng).
Inputs: origin (required), destination (required), field_mask, travel_mode, +3 more.
Convert an address to lat/lng (forward: pass address), or lat/lng to an address (reverse: pass latitude and longitude). Use when the user needs coordinates or a normalized address, or before places_nearby. To find businesses use places_search_text; directions accepts addresses directly, so geocoding first is not required. Returns formatted address, lat/lng, place_id, types, and plus code.
Inputs: address, latitude, longitude, field_mask, +1 more.
Get details for one known place by place_id (from places_search_text or places_nearby). Use when the user asks for a specific place's phone number, website, opening hours, or rating. Returns name, formatted address, lat/lng, rating, opening hours, phone, website, and attributions.
Inputs: place_id (required), field_mask, language_code.
List places within a radius (meters) of a lat/lng you already have, such as the user's location or a geocode result, optionally filtered by Places types (e.g. ["restaurant"]) and ranked by DISTANCE or POPULARITY. For free-text, name, or city queries use places_search_text instead. Returns place_id, name, formatted address, lat/lng, types, rating, opening hours, and attributions.
Inputs: radius (required), latitude (required), longitude (required), field_mask, +4 more.
Find places by free text: a business name, a category, or "X in/near Y" (e.g. "coffee in Porto", "pharmacies near Lisbon Oriente"). Default choice for finding places. Use places_nearby only when you already have exact coordinates. Returns up to 20 places, each with place_id, name, formatted address, lat/lng, types, rating, opening hours (open_now and weekly hours), and attributions. Pass a place_id to places_details for phone or website.
Inputs: query (required), radius, latitude, longitude, +4 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Geoapify MCP — wraps the Geoapify Location Platform (geoapify.com)
Real-time Google Maps local business leads, reviews, places & emails MCP. OAuth or API key.
Geocode, reverse-geocode, autocomplete, route and search places.
Google Maps MCP Pack — geocoding, places, directions, distance matrix, elevation. Uses Google Maps…
Add one secure layer between your agents and this server.