Skip to main content
Glama
tmedford

ubereats-order-history-mcp

by tmedford
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ubereats-order-history-mcp

No user-submitted related servers found.

    Related Servers

    • Uber Eats MCP Server

      matiasconcha11
      F
      license
      A
      quality
      D
      maintenance
      Allows AI assistants to browse menus, manage carts, and place orders on Uber Eats through natural language commands.
      34
      2
      -

    • aliexpress-mcp

      maxwellmezadre
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides read-only access to a user's AliExpress purchase history, including orders, products, price breakdowns, shipping, refunds, and spending summaries, with local caching.
      16 npm
      MIT

    • Yandex Eats MCP

      sptmru
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching restaurants and menu items, viewing availability and full menus, and managing restaurant carts via the private Yandex.Eats web API, secured with single-user OAuth, without exposing sensitive account or location data.
      8 npm
      MIT

    • amazon-mcp

      maxwellmezadre
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables read-only access to a user's Amazon.com.br purchase history, including orders, products, prices, shipping, promotions, reward points, installments, invoices, and spending summaries, with a local SQLite cache.
      12 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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools are mostly distinct: auth check vs. fetching orders, details, transactions, and exporting. However, get_ubereats_orders and get_ubereats_order_details could be confused (both return details), though the former is a list and the latter a single order. Also, get_ubereats_transactions and the receipt in details overlap slightly.

    Naming Consistency5/5

    All tools follow a consistent pattern: check_ubereats_auth_status, get_ubereats_orders, get_ubereats_order_details, get_ubereats_transactions, export_ubereats_csv. The verb_noun format is uniform, and the resource is clearly prefixed with 'ubereats'.

    Tool Count5/5

    With 5 tools, this is well-scoped for the domain of reading Uber Eats data (auth check, order list, order detail, transactions, export). Each tool has a clear, non-redundant purpose, and the count is ideal for a focused connector.

    Completeness3/5

    The set covers read and export operations comprehensively, but there is no update/delete or order mutation (e.g., reorder, cancel) since this is a read-only connector. The missing ability to filter or summarize directly might be a gap, but the core purpose of retrieving and exporting order history is covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources