Skip to main content
Glama
markswendsen-code

@striderlabs/mcp-lyft

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @striderlabs/mcp-lyft

No user-submitted related servers found.

    Related Servers

    • @striderlabs/mcp-uber

      markswendsen-code
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server connector for Uber ride-sharing, enabling ride requests, fare estimates, and trip tracking via browser automation.
      12 npm
      1
      MIT

    • LinkedIn MCP Server

      prakharagarwal-dev
      A
      license
      A
      quality
      A
      maintenance
      A standalone MCP server that exposes typed LinkedIn capabilities (jobs, people, companies, posts, invitations, messaging) through the visible LinkedIn web UI, enabling workflow automation.
      31
      37 PyPI
      3
      Apache 2.0

    • linkedin_mcp

      devleads
      F
      license
      A
      quality
      C
      maintenance
      MCP server for automating LinkedIn actions such as reading feeds, sending messages, creating posts, and managing connections. Uses browser automation with proxy and stealth support.
      21
      -

    • mcp-zen

      mikesmullin
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets MCP clients control a live Zen/Firefox browser to navigate, click, fill forms, screenshot, and execute JavaScript through a persistent server and browser extension.
      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.6/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but 'status' and 'get_ride_status' could be confused at first glance. Descriptions clarify that 'status' is about session/login state, while 'get_ride_status' is about a specific ride, so the ambiguity is minimal.

    Naming Consistency3/5

    Tool names mix standalone verbs (login, logout, status) with verb_noun patterns (set_pickup, get_fare_estimate, request_ride). The inconsistency is noticeable but still readable, with clear conventions for core operations.

    Tool Count5/5

    With 11 tools, the server is well-scoped for a Lyft ride-hailing workflow, covering authentication, trip setup, fare estimation, booking, status, cancellation, and history. Each tool serves a clear purpose without unnecessary bloat.

    Completeness4/5

    The core ride lifecycle is well covered: login, set pickup/destination, estimate/options, request, status, cancel, and history. Minor gaps include no explicit ride-type selection in request_ride (only via get_ride_options) and lack of payment management, but these are workable.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources