ubereats-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UE_LOCALE | No | Interface language for Uber Eats. Set to 'jp' for the Japanese interface. Default is 'en'. | en |
| OPENCLI_BIN | No | Path to the opencli binary. Only needed if opencli is not located at ~/.npm-global/bin/opencli. | ~/.npm-global/bin/opencli |
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 |
|---|---|
| ue_policyA | Read the ordering policy: whether ordering is enabled, per-order / per-day caps (in the account's currency), how much was already spent today, and whether the user is logged in to Uber Eats in Chrome. Use this when:
|
| ue_searchA | Search Uber Eats (delivers to the account's current address; works in any country Uber Eats serves). Works with store names, dishes and products. Product searches (e.g. 'Gatorade', 'ポカリスエット') return supermarkets / drugstores together with the matching items and prices. Use this when:
|
| ue_storeA | A store's menu: item ids, names, prices, sections, quick-add, sold out. Notes:
|
| ue_addA | Add one item to the cart (a write action). spec = option keywords, space-separated, one per option group (e.g. 'Coke Large' / 'コーラ ポテト(L)'; multi-level options are matched level by level); qty = quantity 1-10. Confirm with ue_cart afterwards. Notes:
|
| ue_cartA | List the carts (one per store): draft_id, store, items, most recently changed first. Use this when:
|
| ue_reviewA | Checkout snapshot for one cart — the only trusted price: store / items / options / subtotal / every fee / total / ETA / delivery address / payment method. Read from Uber's checkout API keyed by draft (not the page), with two independent anchors that throw instead of mixing two carts. Returns a confirm_token (valid ~10 min, single use). Use this when:
|
| ue_placeA | Place the order. Requires the confirm_token from ue_review; the checkout snapshot is re-read and must still match (total / store / cart) and be within the per-order / per-day caps — otherwise it refuses. Use this when:
Notes:
|
| ue_ordersA | Active orders and delivery progress. Use this when:
|
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 8 tools
Each tool maps to a distinct stage of the ordering workflow (policy, search, store, add, cart, review, place, orders) with no overlapping purposes. The descriptions reinforce the intended sequence, so an agent can reliably pick the right tool.
All tools share a consistent 'ue_' prefix and single-token names, which is highly readable. It mixes nouns (ue_policy, ue_cart, ue_orders) and verbs (ue_search, ue_add, ue_place) rather than a strict verb_noun pattern, but the convention is still predictable.
Eight tools map cleanly onto the browse → add → review → place → track lifecycle, with each tool earning its place. Nothing feels redundant or missing for the stated ordering purpose.
The core ordering lifecycle is fully covered with safety gates (policy, review, place, orders). Minor gaps exist: there is no way to remove/modify items from a cart, clear a cart, or cancel an order, which an agent cannot fully work around.