goplaces MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_PLACES_API_KEY | Yes | Google Places API key with Places API (New) enabled. Required to run the goplaces MCP server. | |
| GOOGLE_PLACES_BASE_URL | No | Optional base URL for the Google Places API. | https://places.googleapis.com/v1 |
| GOOGLE_ROUTES_BASE_URL | No | Optional base URL for the Google Routes API. | https://routes.googleapis.com |
| GOOGLE_DIRECTIONS_BASE_URL | No | Optional base URL for the Google Directions API. | https://routes.googleapis.com |
| GOOGLE_PLACES_TIMEOUT_SECONDS | No | Optional timeout in seconds for Google Places API requests. | 10 |
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 |
|---|---|
| goplaces_searchA | Search Google Places by free-form text. Use for finding businesses, landmarks, venues, restaurants, shops, attractions, or services. Supports filters for open now, rating, price, type, pagination, and optional circular location bias. Returns compact place summaries and a next_page_token when Google provides one. |
| goplaces_nearbyB | Search Google Places near a latitude/longitude within a radius. Use when the user gives coordinates or you already resolved a location. Returns compact place summaries. |
| goplaces_autocompleteA | Autocomplete a partial place or query string using Google Places. Use to turn partial user input into place/query suggestions and place IDs. |
| goplaces_detailsA | Fetch rich Google Place Details by place ID. Use after search, nearby, autocomplete, or resolve when the user needs phone, website, hours, business status, reviews, or photos. Reviews and photos are opt-in because they are heavier fields. |
| goplaces_photoA | Resolve a Google Places photo resource name into a photo media URL. Use with photo names returned by goplaces_details(include_photos=true). |
| goplaces_resolveA | Resolve a free-form location string into candidate Google places with coordinates and place IDs. Use before nearby searches or directions when you need structured candidates for an address, landmark, city, or venue. |
| goplaces_directionsA | Get directions, distance, duration, warnings, and optional steps between two locations using Google Routes. Each endpoint can be specified by text, place ID, or latitude/longitude. Supports walk, drive, bicycle, transit, units, departure/arrival time, drive avoid modifiers, and one compare mode. |
| goplaces_route_searchA | Find places along a route between two locations, ranked by how little they detour from it. Returns each result's detour time plus the direct route's distance and duration. Use for requests like 'coffee stops between Seattle and Portland' or 'EV charging on the way to Portland'. |
| goplaces_route_matrixA | Rank destinations by travel time and distance from one or more origins in a single request. Use for 'which of these is closest to home' or 'how long to each of these three offices' instead of one directions call per candidate. Results are sorted fastest first. |
| goplaces_reverse_geocodeA | Identify what is at a latitude/longitude by finding the nearest places, closest first, with the distance from the point. Use for 'what is at these coordinates' or to label a GPS position. |
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 10 tools
Most tools target clearly distinct actions (directions, photo, details, route_matrix), but search/resolve/autocomplete all convert text into places, and nearby/reverse_geocode both find places near coordinates. Descriptions provide use-case cues, so an agent can usually pick correctly, but the boundaries are not perfectly sharp.
All tools share the goplaces_ prefix and snake_case naming with clear action/resource terms. There is no mixing of conventions such as camelCase, hyphens, or vague names.
10 tools are well-scoped for a Google Places/Routes MCP, covering distinct API surfaces without obvious filler. Each tool maps to a meaningful location or routing capability.
The set covers search, nearby, autocomplete, details, photos, resolution, directions, route search, route matrix, and reverse geocoding. For a read-only places/routes domain, this provides comprehensive workflow coverage with no major dead ends.