mcp-google-map and open-streetmap-mcp
These are complements that serve different use cases: Google Maps MCP excels at routing, traffic, and business location data, while OpenStreetMap MCP provides open-source vector tile access and offline-capable mapping, allowing developers to choose based on proprietary vs. open-data requirements.
About mcp-google-map
cablate/mcp-google-map
A powerful Model Context Protocol (MCP) server providing comprehensive Google Maps API integration with LLM processing capabilities.
Exposes 18 geospatial tools (geocoding, routing, elevation, air quality, place search) across stdio, HTTP, and CLI modes, with built-in tool-chaining optimization via the Routes API for multi-stop waypoint ordering. Includes an agent skill definition that teaches LLMs how to compose these tools sequentially, plus features like local search ranking tracking and context-reduction via selective tool registration.
About open-streetmap-mcp
jagan-shanmugam/open-streetmap-mcp
An OpenStreetMap MCP server implementation that enhances LLM capabilities with location-based services and geospatial data.
Implements 12+ geospatial tools including geocoding, routing, POI discovery, and neighborhood analysis through a stdio-based MCP server compatible with Claude Desktop, Cursor, and Windsurf. Built on OpenStreetMap data with resources for place lookups and styled map tiles, enabling LLMs to power location-aware applications like meeting point optimization, commute analysis, and real estate evaluation. Uses Python with the MCP framework and includes example clients demonstrating both basic tool invocation and LLM integration patterns.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work