Skip to main content
Glama
oakley7247

google-maps-harness

by oakley7247
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to google-maps-harness

No user-submitted related servers found.

    Related Servers

    • Google Maps MCP Server

      Garblesnarff
      A
      license
      B
      quality
      D
      maintenance
      Provides 14 comprehensive tools for geocoding, navigation, and visual mapping using Google Maps APIs. It also offers detailed environmental data including weather forecasts, air quality indices, and solar irradiance for location-based analysis and trip planning.
      14
      10
      MIT

    • Google Maps MCP Server

      iceener
      F
      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
      -

    • Google Maps MCP Server

      AIWerk
      A
      license
      A
      quality
      C
      maintenance
      Provides access to Google Maps Platform APIs for places search, geocoding, turn-by-turn directions, route matrices, elevation, and time zones. Enables natural language queries for location-based information and routing.
      11
      12 npm
      MIT

    • mcp-google_maps

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      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.
      29 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

    A4.3/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: geocoding tools separate address, coordinate, and place ID lookups; search tools differ by text query vs. nearby; compute_route vs. compute_route_matrix are well-differentiated. However, search_places_by_text and search_places_nearby could overlap in some use cases (e.g., 'restaurants near me' vs. a point), and the descriptions partially compensate.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout (e.g., geocode_address, search_places_by_text, compute_route, get_place_details). All names are descriptive and predictable, making it easy to infer what each tool does from its name alone.

    Tool Count5/5

    With 13 tools, the set is well-scoped for a Google Maps MCP server. Each tool covers a distinct geographic or mapping function—geocoding, search, routing, elevation, time zone, air quality, validation—without unnecessary bulk. The count feels complete and not overwhelming.

    Completeness4/5

    The server covers a comprehensive set of mapping operations: geocoding (forward, reverse, place ID, validation), place search (text, nearby, autocomplete, details), routing (single and matrix), and supplemental data (elevation, time zone, air quality). A minor gap is the lack of a tool for displaying maps or static map images, but this is not core to the MCP paradigm.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources