Skip to main content
Glama
Ocean-Ch

google-maps-transit

by Ocean-Ch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to google-maps-transit

No user-submitted related servers found.

    Related Servers

    • maps-mcp

      snickery
      A
      license
      A
      quality
      B
      maintenance
      MCP server exposing Google Maps Platform to MCP clients with seven tools for geocoding, place search/details, traffic-aware travel times, and time zones. Runs as a local stdio server or a containerized HTTP service with bearer auth, needing only a single API key.
      7
      MIT

    • MCP Google Map Server

      cablate
      A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that provides Google Maps API integration, allowing users to search locations, get place details, geocode addresses, calculate distances, obtain directions, and retrieve elevation data through LLM processing capabilities.
      7
      504 npm
      450
      MIT

    • beaver-mcp

      alanko0511
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides Google Maps search, navigation, and travel time estimation alongside Lunch Money financial management, all accessible via a Cloudflare Workers MCP server with OAuth authentication.
      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.2/5.0

    Scored across 4 tools

    Disambiguation4/5

    search_places and get_place_details are cleanly separated as search vs. detail lookup, and the commute tools have distinct scopes (point-to-point vs. multi-origin ranking). The only mild overlap is between get_transit_commute and compare_commutes, both of which compute routes, though the descriptions make the boundary fairly clear.

    Naming Consistency5/5

    All four tools follow a consistent snake_case verb_noun pattern: get_transit_commute, search_places, get_place_details, compare_commutes. The convention is predictable and self-explanatory.

    Tool Count4/5

    Four tools is slightly lean for a maps server covering both routing and place discovery, but each tool earns its place and there is no redundancy. It is well-scoped, just on the minimal side.

    Completeness4/5

    The surface covers commute/routing (including multi-leg and comparison ranking) and a full place search-plus-detail lifecycle. Minor gaps exist—no standalone distance matrix, geocoding, or turn-by-turn directions—but core agent workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources