Uber Eats MCP. Manage order flow and inventory across all locations.

This MCP Server connects your AI client directly to the full Uber Eats Merchant API. You get complete operational control—managing orders, updating menus, and handling store logistics—all through natural language commands. Your agent can run the entire restaurant cycle without you having to click around in a dashboard.

Managing Order Flow: From Ping to Paycheck

You handle the whole order lifecycle right here. First, you use get_orders to list every single delivery across all your locations, letting you filter by status—PENDING, READY, DELIVERED, and everything in between. When a new order comes in, you pull all the details for that specific job using get_order, which gives you the item list, instructions, and total amount before staff even start prepping.

If the kitchen is swamped or something’s wrong with the ticket, your agent can decline it immediately using reject_order and provide a required reason code. If an order was accepted but needs to be scrapped entirely, you use cancel_order, which forces you to specify a cancellation reason code for records.

When everything looks good, you confirm preparation starts by calling mark_order_prep_started; that tells the customer and the system your staff are on it. Once the food is packaged up and ready to go, you signal this using mark_order_ready, which triggers the courier dispatch notification. When the meal finally lands at the door, you use complete_order to finalize the order's record and trigger final payment processing for accounting.

Monitoring Deliveries and Issues

Tracking is simple. You get real-time location data, estimated time of arrival (ETA), and status updates for every active delivery using get_delivery_status. If there’s a dispute or complaint attached to an order, you don't have to guess what happened; calling get_order_issues pulls up the list of reported complaints and timestamps so you can address it head-on.

You can also check the general operational status for your entire set of locations using get_stores, or dive into specific setup details for one spot with get_store.

Inventory Control and Menu Updates

You control what's on the menu and if it's available. Before you mess with anything, you can pull the full catalog structure for a location using get_menus, which gives you all the necessary item IDs needed to make changes later. To update stock levels, your agent uses update_menu_item_availability—you just toggle an item’s status as in-stock or out-of-stock using its unique menu ID.

The Process In Action

Your AI client takes the whole mess of operational data and turns it into simple actions. It reads all the tools, understands your intent—like 'Accept pending orders for Store B and mark the lasagna unavailable'—and runs those necessary functions sequentially. It handles everything from accepting an order via accept_order to updating inventory through update_menu_item_availability, letting you manage every part of the restaurant operation with plain language commands.