goplaces MCP
Related Servers
Alternatives to goplaces MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides custom tools to the Gemini model for spatially grounding responses using Google Maps Platform APIs (Places, Routes, Elevation).64Apache 2.0
- FlicenseAqualityCmaintenanceGives Claude and other MCP clients access to Google Maps Platform: geocoding, place search, place details, directions, distance matrix, and elevation.7-
- AlicenseAqualityDmaintenanceEnables LLM clients to convert addresses to coordinates (forward geocoding), coordinates to addresses (reverse geocoding), and lookup Google Place IDs using the Google Maps Geocoding API with support for multiple languages and advanced filtering.310MIT
- AlicenseAqualityCmaintenanceProvides access to Google Maps Platform APIs for places search, geocoding, turn-by-turn directions, route matrices, elevation, and time zones. Enables natural language queries for location-based information and routing.117MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to access Google Maps services including geocoding, place search, directions, distance calculations, and elevation data through stdio communication. Provides comprehensive location-based functionality with direct Google Maps API integration.MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Maps API for geocoding, place search, directions, distance matrices, and elevation data through natural language.MIT
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.