Enterprise DNA
M MCP Servers Developer low

cablate/mcp-google-map

by Various

A powerful Model Context Protocol (MCP) server providing comprehensive Google Maps API integration with LLM processing capabilities.

C

MCP

cablate/mcp-google-map

Added 1 June 2026

#agent-skill #ai #ai-agent #dive #geocoding #geospatial #google-map #google-maps

Overview

An MCP server that wraps Google Maps API endpoints for use with LLM agents. It exposes place search, geocoding, directions, and elevation data through the Model Context Protocol, letting AI assistants query map services directly.

Best for

Best for
Developers building LLM agents that need real-world location and navigation data

Use cases

  • Let an LLM agent find nearby restaurants or businesses by category and location
  • Get turn-by-turn driving or walking directions between two addresses
  • Retrieve elevation data for a set of geographic coordinates

Notes

An MCP server that wraps Google Maps API endpoints for use with LLM agents. It exposes place search, geocoding, directions, and elevation data through the Model Context Protocol, letting AI assistants query map services directly.

322 stars on GitHub. Last updated 2026-04-21. Licensed MIT.

Use cases

  • Let an LLM agent find nearby restaurants or businesses by category and location
  • Get turn-by-turn driving or walking directions between two addresses
  • Retrieve elevation data for a set of geographic coordinates

Pros

  • 322 GitHub stars indicate community trust and active use
  • Written in TypeScript with typed interfaces for reliable integration
  • Covers multiple Google Maps API features in one MCP server

Cons

  • Requires a Google Maps API key with billing enabled, adding cost
  • Limited to Google Maps data, no support for alternative map providers
  • Dependent on MCP protocol adoption by the LLM client or framework

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • 322 GitHub stars indicate community trust and active use
  • Written in TypeScript with typed interfaces for reliable integration
  • Covers multiple Google Maps API features in one MCP server

Cons

  • Requires a Google Maps API key with billing enabled, adding cost
  • Limited to Google Maps data, no support for alternative map providers
  • Dependent on MCP protocol adoption by the LLM client or framework