Skip to main content
Glama
Sign In
google-maps-mcp

google-maps-mcp

by benjamin-di
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to google-maps-mcp

No user-submitted related servers found.

    Related Servers

    • Google Maps MCP Server

      adityak74
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to search places, retrieve place details, reviews, photos, business posts, and contributor review histories from Google Maps through natural language, with no API keys or paid billing required.
      6
      MIT

    • Google Maps MCP Server

      iceener
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables location-aware AI agents to search for nearby places, get detailed place information including hours and ratings, and calculate routes with turn-by-turn directions using Google Maps APIs.
      22
      MIT

    • mcp-google_maps

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides geocoding, place search, directions, distance matrix, and elevation data from Google Maps. Enables natural language queries to locate places, get directions, and retrieve map-related information.
      148 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation3/5

    Most tools map to distinct operations, but maps_compute_route and maps_plan_route both compute multi-stop travel times with substantially overlapping output fields, and maps_show_route is explicitly described as carrying the 'same facts as maps_plan_route,' so an agent can easily pick the wrong one when it only needs data or only needs a card. The descriptions do provide guidance ('Use it whenever you give directions'), which keeps this from being worse than moderate overlap.

    Naming Consistency4/5

    All tools share a consistent maps_ prefix and mostly follow verb_noun (get_place, search_places, compute_route, plan_route, show_places). The only deviations are the noun-only maps_static_map and maps_status, which are minor and still unsurprising.

    Tool Count5/5

    Nine tools is well within a comfortable range and each one earns its place: place lookup/search/rendering, route compute/plan/render, a matrix variant, a static image, and diagnostics. No obviously redundant or filler tools.

    Completeness4/5

    The surface covers the core Maps workflows: place discovery and detail, routing (single, multi-stop with optimization and dwell), pairwise matrices, map imagery, and a health/budget check. Minor gaps remain, such as address geocoding/autocomplete as first-class operations and route alternatives, but agents can work around these via textQuery search.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources