maps-mcp
Related Servers
Alternatives to maps-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceComprehensive MCP server for Google Maps APIs, enabling geocoding, place search and details, distance matrix, elevation, and directions through natural language.6-
- FlicenseNot gradedqualityBmaintenanceA general-purpose Google Maps MCP server that provides geocoding, place search, directions, distance matrices, and time zone lookup over the Model Context Protocol.-
- AlicenseNot gradedqualityBmaintenanceA TypeScript MCP server that exposes Google Maps Platform APIs as tools for LLMs, providing real map data like directions, transit routes, place search, address validation, photos, and elevation.17 npm9GPL 3.0
- AlicenseAqualityCmaintenanceProduction-ready MCP server for Google Maps Platform APIs, providing 11 tools for directions, places, geocoding, traffic, and road data to empower AI agents with location intelligence.114Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools for Google Maps services including directions, geocoding, distance matrix, and places search.14Apache 2.0
- FlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server for Google Maps — routing, place discovery, and commute comparison over stdio.41-
TDQS
Scored across 7 tools
Each tool targets a distinct operation: geocoding forward/reverse, place search by text or type, place details by ID, routing, and timezone lookup. Even place_search and place_search_nearby are clearly separated by free-text vs. type/radius queries with distinct parameters, leaving no ambiguity.
All names are lowercase with underscores and readable, but the pattern is mixed: geocode and reverse_geocode are verb-first, while place_search, place_details, travel_time, and time_zone are noun-first. This is a minor inconsistency that does not harm clarity.
Seven tools cover the core map-related operations without redundancy or bloat. The scope is well-balanced, fitting a focused maps MCP server that handles geocoding, place discovery, routing, and timezone data.
The surface provides a complete life-cycle for map queries: geocoding both directions, place discovery via text and type, detailed place information, travel time/directions, and timezone data. No major gaps for the stated purpose, and all operations are read-only which suits the domain.