ubereats-order-history-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UBEREATS_LOCALE | No | localeCode sent to Uber Eats. | en-US |
| UBEREATS_TIMEZONE | No | Zone used to turn timestamps into YYYY-MM-DD for date filters. | system zone |
| UBEREATS_CHROME_PATH | No | Chrome binary to drive. | /Applications/Google Chrome.app/... |
| UBEREATS_CHROME_PROFILE | No | Chrome profile to read cookies from (Default, Profile 1, ...). | Default |
| UBEREATS_ORDERS_HEADFUL | No | Set to '1' to show the browser window (debugging). | |
| UBEREATS_CHROME_PROFILE_DIR | No | Full path to the Chrome profile directory to use instead of the default profile. | |
| UBEREATS_ORDERS_BROWSER_DATA_DIR | No | The connector's own browser profile (never Chrome's). | ~/.ubereats-order-history-mcp/browser-data |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_ubereats_auth_statusA | Check whether the connector is signed in to Uber Eats. It reuses the session from your Google Chrome (cookies are copied from Chrome on every start and whenever a call finds the session expired) - it never asks for a password. |
| get_ubereats_ordersA | List Uber Eats orders newest-first, read from Uber Eats' own order-history feed: store, dates, status, every item with quantity/unit price/options, and the fare breakdown (subtotal, tax, delivery fee, service fee, tip, discounts, total). Stops paging as soon as it passes start_date. Set include_receipts to also attach each order's card charges. |
| get_ubereats_order_detailsA | Everything about one Uber Eats order: items and options, fare breakdown, and (by default) its receipt - every card charge, separately-billed tip and refund with the card brand, last 4 digits, amount and time, plus pickup/drop-off addresses. |
| get_ubereats_transactionsA | Every card charge and refund Uber Eats made, one row each - the shape of a card statement: charge time, amount, card brand + last 4, the order and store it paid for, and whether it is a tip billed after delivery. Use this to match bank/card transactions to orders. Charges are kept by their own date, so a tip or refund that posted days after the order is included. |
| export_ubereats_csvA | Write orders, line items or card transactions to a CSV file (default ~/Downloads). Returns the path and row count. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.