A
licenseA
qualityD
maintenanceProvides access to Google Maps API functionality including places search, geocoding, directions, distance matrix, elevation data, and static map generation through the MCP interface.
8
5 npm
1
MIT
Google Maps MCP Server
by Moe03
Related Servers
Alternatives to Google Maps MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceProvides comprehensive access to Google Maps Platform APIs through MCP, enabling geocoding, places search, routing, and geospatial operations.15122 npm3MIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools for Google Maps services including directions, geocoding, distance matrix, and places search.14Apache 2.0
- FlicenseNot gradedqualityDmaintenanceComprehensive MCP server for Google Maps APIs, enabling geocoding, place search and details, distance matrix, elevation, and directions through natural language.6-
- FlicenseNot gradedqualityDmaintenanceIntegrates with Google Places API to allow searching, retrieving details, and finding nearby places through an MCP server interface.-
- FlicenseNot gradedqualityDmaintenanceA general-purpose Google Maps MCP server that provides geocoding, place search, directions, distance matrices, and time zone lookup over the Model Context Protocol.-
TDQS
C2.9/5.0
Scored across 4 tools
Disambiguation2/5
Three tools (add_post, delete_post, get_posts) clearly relate to a posts/CRUD domain, while get_weather is unrelated to posts and creates a domain mismatch. Within the posts tools, there is good disambiguation (add, delete, get), but the inclusion of weather introduces significant ambiguity about the server's purpose and tool boundaries.
Naming Consistency4/5
The naming follows a consistent verb_noun pattern (add_post, delete_post, get_posts, get_weather) with clear actions and objects. All tools use snake_case uniformly, making them readable and predictable, though the weather tool's domain deviation slightly affects overall consistency.
Tool Count3/5
With 4 tools, the count is reasonable, but it feels thin for a 'Google Maps MCP Server' as it lacks core mapping functionalities (e.g., geocoding, directions, places search). The tools present cover a basic posts system and weather, which is mismatched with the server name, making the scope unclear and borderline inappropriate.
Completeness2/5
For a posts domain, the tools provide basic CRUD (add, delete, get) but lack update functionality, creating a minor gap. More critically, for a Google Maps server, there are no mapping-related tools (e.g., search_places, get_directions), resulting in significant gaps that will cause agent failures in handling mapping tasks.
Maintenance
ActivityInactive
ResponsivenessNo issues