ubereats-order-history-mcp
Related Servers
Alternatives to ubereats-order-history-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to list Uber Eats orders, fetch itemized receipt and summary files, and update group-order debt ledgers that preserve existing rows and paid state. It also exports a live Safari browser session cookie to a private file for authentication.MIT
- FlicenseAqualityDmaintenanceAllows AI assistants to browse menus, manage carts, and place orders on Uber Eats through natural language commands.343-
- AlicenseAqualityBmaintenanceEnables downloading Amazon order history as CSV files with support for orders, items, shipments, and transactions across 16 Amazon regional sites using browser automation.1230 npm24MIT
- AlicenseAqualityBmaintenanceEnables an AI agent to search stores and dishes, browse menus, add items with options and quantities, and read a checkout snapshot inside the user's own logged-in Chrome session, placing an order only after explicit approval. Ordering is gated behind a review step with a one-time confirm token, spend caps, and post-order delivery tracking, while card numbers and addresses never appear in the conversation.816AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceProvides read-only access to a user's AliExpress purchase history, including orders, products, price breakdowns, shipping, refunds, and spending summaries, with local caching.11 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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.6 npmMIT
TDQS
Scored across 5 tools
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.
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'.
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.
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.