Skip to main content
Glama
nathanielangafor

Waymo MCP

by nathanielangafor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Waymo MCP

No user-submitted related servers found.

    Related Servers

    • Travel MCP

      RagnarLothbrok20
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides mock travel planning tools including flight and hotel search, recommendations, and multi-turn trip drafting. Supports stdio and HTTP transports and is intended for testing/demo purposes only.
      -

    • Subaru STARLINK MCP for Grok

      elderibeiro
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables a local Grok Bot to talk to the unofficial MySubaru API over stdio, supporting vehicle status, locate, tire pressure, fuel, odometer, climate presets, and explicit lock/unlock/remote start actions without exposing secrets.
      1
      MIT

    • tripit-mcp

      jerhinesmith
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to your TripIt trips and full itineraries, including flights, hotels, car rentals, and activities, over stdio.
      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

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool maps to a distinct phase of the Waymo rider workflow: place search, quote, booking, cancellation, payment methods, trip history, and active ride status. The two ride-related tools are separated by historical trips versus active/cached status, so there is no meaningful overlap.

    Naming Consistency4/5

    Most tools follow a clear waymo_<verb>_<noun> pattern such as get_quote, book_ride, and cancel_ride. waymo_ride_history and waymo_ride_status break the pattern by leading with a noun, but the shared prefix and consistent snake_case keep the set readable.

    Tool Count5/5

    Eight tools is well-scoped for a ride-hailing server: the set covers discovery, quoting, booking, cancellation, payments, and trip lookups without unnecessary duplication. Each tool serves a concrete user-facing need.

    Completeness4/5

    The core rider lifecycle is well covered: search places, get a quote, book, cancel with fee preview, list payment methods, and retrieve history/status. There are minor gaps like no explicit way to fetch details for an arbitrary past trip or manage payment methods, but these do not block the main workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources