Local services & SaaS
DoorDash
Search stores, build carts and order on your DoorDash account.
14 endpoints
Uber's Eats APIs may require written approval from Uber, and its ChatGPT integration is for eaters (checked 16 Nov 2026). Cotlet runs a hosted Uber Eats MCP server with 17 tools that ChatGPT and Claude use in your own merchant account: menus, holiday hours, store status and orders. Anything eaters see waits for your OK.
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Uber Eats. Uber Eats is a trademark of its owner. If Uber Eats's own integrations cover what you need, use them first.
17 tools Read and write
Uber documents Eats APIs for menus, orders and stores, and each reference page says access may require written approval from Uber. Uber's official ChatGPT integration is for eaters: in the US it shows restaurants and menus, and checkout happens in the Uber Eats app. No official ChatGPT or Claude connector for running a restaurant was found.
| What you need | Uber Eats API | Manager by hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to run your store | Eater app only | Copy and paste | Hosted MCP server |
| Start today with your own login | Uber's approval first | Your login | Your login, once |
| Menus, hours and store status | After approval, your code | One store at a time | Every store, after your OK |
| Run from n8n or a script | Your own integration | Manual only | REST, same key |
Checked 16 Nov 2026. Sources: Uber Help: ChatGPT Integration for Eaters · Uber Eats for merchants · API: Get Menu · API: Upload Menu · API: Update Item · API: Get Order Details · API: Created Orders · API: Canceled Orders · API: Accept Order · API: Deny Order · API: Cancel Order · API: Update Cart · API: Restaurant Delivery Status · API: Stores · API: Store Details · API: Store Status · API: Set Store Status · API: Holiday Hours · API: Set Holiday Hours
Once, in a browser we host for you.
One address in its settings.
It changes every store after your OK.
Your agent works in your own signed-in Cloud Browser. Menu changes, store pauses and order actions wait for your OK. Who can see your session
Sign in to Uber Eats Manager in a Cloud Browser. Open merchants.ubereats.com/manager in your Cotlet Cloud Browser and sign in with your merchant user.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
Uber Eats lives on the shared address https://cotlet.dev/mcp/v1 next to every other app you turn on, so your POS, booking and delivery apps can share one connector. Turned on Uber Eats later? Refresh the connector and its 17 tools appear.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: uber_eats_read One tool per restaurant action Uber documents for Eats: stores, hours, menus and orders. Every write asks first.
Your stores, whether each is taking orders, and holiday hours. Saving holiday hours replaces the old set, so the agent reads them first.
Usually the first call for a group with several locations: the other tools take one of these stores. Reading changes nothing.
MCP calluber_eats_read → list_stores
REST endpointGET https://cotlet.dev/api/v1/uber-eats/stores
No parameters.
{
"stores": [
{
"store": "Example Noodle Bar, Main St"
},
{
"store": "Example Noodle Bar, Harbour"
}
]
} Returns the details Uber Eats holds for the store. Reading changes nothing.
MCP calluber_eats_read → get_store
REST endpointGET https://cotlet.dev/api/v1/uber-eats/store
| Name | Type | Description |
|---|---|---|
| store string required | string | The store, by its name in Uber Eats Manager or as list_stores returns it. |
{
"store": "store"
} {
"store": "Example Noodle Bar, Main St",
"address": "12 Main St, Springfield",
"phone": "+1 555 0100"
} Returns the store's current status on Uber Eats, for example whether it is taking orders. Run it before set_store_status, so you know what you are changing.
MCP calluber_eats_read → get_store_status
REST endpointGET https://cotlet.dev/api/v1/uber-eats/store-status
| Name | Type | Description |
|---|---|---|
| store string required | string | The store, by its name in Uber Eats Manager or as list_stores returns it. |
{
"store": "store"
} {
"store": "Example Noodle Bar, Main St",
"status": "online"
} A paused store takes no new Uber Eats orders until it is back online, so this waits for your OK. Use it when the kitchen is overloaded or closes early. By default you confirm each call; you can switch that off for this tool.
MCP calluber_eats_write → set_store_status
REST endpointPUT https://cotlet.dev/api/v1/uber-eats/store-status
| Name | Type | Description |
|---|---|---|
| store string required | string | The store, by its name in Uber Eats Manager or as list_stores returns it. |
| status string required | string | The status to set, as Uber Eats Manager offers it, for example paused or online. |
{
"store": "store",
"status": "status"
} {
"store": "Example Noodle Bar, Main St",
"status": "paused",
"saved": true
} Uber describes holiday hours as exceptions to the normal operating hours, applied day by day. They come back sorted by date.
MCP calluber_eats_read → get_holiday_hours
REST endpointGET https://cotlet.dev/api/v1/uber-eats/holiday-hours
| Name | Type | Description |
|---|---|---|
| store string required | string | The store, by its name in Uber Eats Manager or as list_stores returns it. |
{
"store": "store"
} {
"store": "Example Noodle Bar, Main St",
"holiday_hours": [
{
"date": "2026-12-24",
"open": "11:00",
"close": "15:00"
},
{
"date": "2026-12-25",
"closed": true
}
]
} Uber's docs say each save overwrites the holiday hours already set, so the agent reads them with get_holiday_hours first and sends the dates you add together with the ones already there. By default you confirm each call; you can switch that off for this tool.
MCP calluber_eats_write → set_holiday_hours
REST endpointPUT https://cotlet.dev/api/v1/uber-eats/holiday-hours
| Name | Type | Description |
|---|---|---|
| store string required | string | The store, by its name in Uber Eats Manager or as list_stores returns it. |
| days array required | array | Every holiday date to keep, each with its open and close times or `closed: true`. |
{
"store": "Example Noodle Bar, Main St",
"days": [
{
"date": "2026-12-24",
"open": "11:00",
"close": "15:00"
},
{
"date": "2026-12-25",
"closed": true
},
{
"date": "2026-12-31",
"open": "11:00",
"close": "18:00"
}
]
} {
"store": "Example Noodle Bar, Main St",
"holiday_hours": [
{
"date": "2026-12-24",
"open": "11:00",
"close": "15:00"
},
{
"date": "2026-12-25",
"closed": true
},
{
"date": "2026-12-31",
"open": "11:00",
"close": "18:00"
}
],
"saved": true
} New orders oldest first, one order in full, accept or deny, cancel, substitute an out-of-stock item, delivery status for your own drivers, and orders canceled in the last two hours.
Returns orders an eater has placed and the restaurant has not yet accepted or denied, oldest first.
MCP calluber_eats_read → list_new_orders
REST endpointGET https://cotlet.dev/api/v1/uber-eats/new-orders
| Name | Type | Description |
|---|---|---|
| store string required | string | The store, by its name in Uber Eats Manager or as list_stores returns it. |
{
"store": "store"
} {
"store": "Example Noodle Bar, Main St",
"orders": [
{
"order": "A1F3",
"placed": "18:42",
"items": 3,
"total": 41.5
},
{
"order": "B7C9",
"placed": "18:44",
"items": 1,
"total": 14.5
}
]
} Reading changes nothing. Use it before accept_order, deny_order or update_order_cart to see exactly what was ordered.
MCP calluber_eats_read → get_order
REST endpointGET https://cotlet.dev/api/v1/uber-eats/order
| Name | Type | Description |
|---|---|---|
| order string required | string | The order, as list_new_orders or get_order returns it. |
{
"order": "order"
} {
"order": "A1F3",
"store": "Example Noodle Bar, Main St",
"items": [
{
"item": "Beef pho",
"quantity": 2,
"price": 14.5
},
{
"item": "Spring rolls",
"quantity": 1,
"price": 8
},
{
"item": "Iced tea",
"quantity": 1,
"price": 4.5
}
],
"total": 41.5,
"note": "No cilantro"
} Accepting tells the eater the restaurant is making the order. By default you confirm each call; you can switch that off for this tool.
MCP calluber_eats_write → accept_order
REST endpointPOST https://cotlet.dev/api/v1/uber-eats/order/accept
| Name | Type | Description |
|---|---|---|
| order string required | string | The order, as list_new_orders or get_order returns it. |
{
"order": "order"
} {
"order": "A1F3",
"status": "accepted"
} The eater does not get the order, so it waits for your OK. Uber notes that a denial does not always cancel the order at once, because the store may still accept it on its in-store tablet. By default you confirm each call; you can switch that off for this tool.
MCP calluber_eats_write → deny_order
REST endpointPOST https://cotlet.dev/api/v1/uber-eats/order/deny
| Name | Type | Description |
|---|---|---|
| order string required | string | The order, as list_new_orders or get_order returns it. |
| reason string required | string | Why, in a few words, for example that an item is unavailable. |
| out_of_stock_items array | array | Items that ran out, as get_order returns them. |
{
"order": "order",
"reason": "reason"
} {
"order": "B7C9",
"status": "denied",
"out_of_stock_items": [
"Spicy ramen"
]
} Only orders still in progress can be canceled; one that is already finished cannot. The eater loses the order, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP calluber_eats_write → cancel_order
REST endpointPOST https://cotlet.dev/api/v1/uber-eats/order/cancel
| Name | Type | Description |
|---|---|---|
| order string required | string | The order, as list_new_orders or get_order returns it. |
| reason string required | string | The cancel reason, from the reasons Uber offers. |
{
"order": "order",
"reason": "reason"
} {
"order": "C2D8",
"status": "canceled"
} Uber checks each change: the substitute must be in stock, must not cost more than the original item, and must match the substitution preference the eater chose. The eater sees the change, so it waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP calluber_eats_write → update_order_cart
REST endpointPATCH https://cotlet.dev/api/v1/uber-eats/order-cart
| Name | Type | Description |
|---|---|---|
| order string required | string | The order, as list_new_orders or get_order returns it. |
| item string required | string | The ordered item to change. |
| action string required | string | `remove` or `replace`. Replace only where the eater allowed a substitute. |
| substitute object | object | For `replace`: the substitute item and quantity. |
{
"order": "order",
"item": "item",
"action": "action"
} {
"order": "A1F3",
"item": "Spring rolls",
"action": "replace",
"substitute": {
"item": "Summer rolls",
"quantity": 1
},
"saved": true
} For orders the restaurant delivers itself. The eater follows the status, so each update waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP calluber_eats_write → update_delivery_status
REST endpointPATCH https://cotlet.dev/api/v1/uber-eats/delivery-status
| Name | Type | Description |
|---|---|---|
| order string required | string | The order, as list_new_orders or get_order returns it. |
| status string required | string | The delivery step the order has reached, as Uber Eats offers it. |
{
"order": "order",
"status": "status"
} {
"order": "D4E1",
"status": "out for delivery",
"saved": true
} Covers orders canceled by the restaurant, in Uber Eats Orders, or by Uber support, newest first, within the last two hours.
MCP calluber_eats_read → list_canceled_orders
REST endpointGET https://cotlet.dev/api/v1/uber-eats/canceled-orders
| Name | Type | Description |
|---|---|---|
| store string required | string | The store, by its name in Uber Eats Manager or as list_stores returns it. |
{
"store": "store"
} {
"store": "Example Noodle Bar, Main St",
"orders": [
{
"order": "E5F0",
"canceled": "18:20",
"total": 19.5
},
{
"order": "C2D8",
"canceled": "17:58",
"total": 27
}
]
} Your signed-in Uber Eats Manager browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 17 Uber Eats tools. The session cookie stays in the Cloud Browser.
The stores your merchant user manages, and nothing more.
Payouts, bank details, tax settings, users and permissions in Uber Eats Manager.
You sign in again yourself, in the same Cloud Browser, with any code Uber sends you.
Disable Uber Eats for agents, reset the browser, or sign out of all sessions in your Uber account.
You sign in to Uber yourself; the agent only uses the session that sign-in leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
| Action | How to put it right |
|---|---|
| Item marked sold out by mistake | Call update_menu_item again with the item available |
| Store paused | Set it back with set_store_status |
| Holiday hours wrong | Save the right full list with set_holiday_hours |
| Order denied, canceled or changed | Already with the eater: it cannot be pulled back |
All 9 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 8 read tools, stores, menus, hours and order lists, run at once.
{
"name": "set_holiday_hours",
"arguments": {
"store": "Example Noodle Bar, Main St",
"days": [
{
"date": "2026-12-24",
"open": "11:00",
"close": "15:00"
},
{
"date": "2026-12-25",
"closed": true
},
{
"date": "2026-12-31",
"open": "11:00",
"close": "18:00"
}
]
}
} curl -X PUT https://cotlet.dev/api/v1/uber-eats/holiday-hours \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"store":"Example Noodle Bar, Main St","days":[{"date":"2026-12-24","open":"11:00","close":"15:00"},{"date":"2026-12-25","closed":true},{"date":"2026-12-31","open":"11:00","close":"18:00"}]}' {
"store": "Example Noodle Bar, Main St",
"holiday_hours": [
{
"date": "2026-12-24",
"open": "11:00",
"close": "15:00"
},
{
"date": "2026-12-25",
"closed": true
},
{
"date": "2026-12-31",
"open": "11:00",
"close": "18:00"
}
],
"saved": true
} The example adds New Year's Eve to a store that already closes early on Christmas Eve and stays shut on Christmas Day, sending all three dates. A cron job or n8n flow can make the same call over REST at /api/v1/uber-eats with the same key and price, in JSON. Failed calls are free.
About $23 a monthfor a restaurant with two Uber Eats stores, 3,980 credits. Uber's fees stay as they are.
| Job | Calls | Credits |
|---|---|---|
| Sold-out items on both stores | 3 × 30 | 900 |
| Canceled orders after dinner | 3 × 30 | 900 |
| Order lookups and substitutions | 2 × 20 | 400 |
| Store pauses and checks | 2 × 8 | 160 |
| Holiday hours | 2 × 2 | 40 |
| Menu reads and price changes | 2 × 4 | 80 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 248 calls | 3,980 |
The smallest pack, 5,000 credits for $29, covers this month. More stores mean more calls.
Credit packs are one-time purchases, not a subscription. The month above is built from our own assumptions, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| Uber Eats APIs through a POS | Menus, orders and stores synced by an approved integration. | Needs Uber's approval; you depend on what your POS builds. |
| Uber Eats in ChatGPT | Eaters in the US browse restaurants and menus. | For eaters, not for running your store. |
| Uber Eats Manager and Orders | Uber's own screens and tablet app. | One store and one screen at a time, by hand. |
If your POS already syncs Uber Eats menus and orders, keep it for incoming orders. Cotlet fits the work around them: sold-out items across stores, holiday hours, pauses and the after-rush review, from the agent you already use.
Take Group sp. z o.o. operates Cotlet.dev. The company is registered in Poland, EU (VAT PL6342984273), has built software since 2019 and is led by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Uber Eats tools: contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=uber-eats, turn on Uber Eats under Integrations in the console and sign in at https://merchants.ubereats.com/manager/ in your Cloud Browser. Then connect your AI agent and ask it about your stores. The trial needs no card.
Partly, behind approval: Uber documents Eats APIs for menus, orders and stores at developer.uber.com, and every reference page says access may require written approval from Uber, with OAuth scopes per app (checked 16 Nov 2026). Uber's official ChatGPT integration is for eaters: it shows restaurants and menus in the US and sends checkout to the Uber Eats app. No official ChatGPT or Claude connector for running a restaurant was found. Cotlet does not use that API: it works in your own signed-in Uber Eats merchant account.
No. Uber's ChatGPT integration lets eaters in the US look at restaurants and menus and finish the order in the Uber Eats app. Cotlet works on the restaurant side: your stores, menus, hours and orders.
No. None of the tools read or change payouts, bank details or tax settings in Uber Eats Manager.
Your tablet or POS stays the main way to take orders as they arrive. accept_order and deny_order are there for follow-up, and each waits for your OK unless you switch that off.
Only in how it is called. Both carry the same 17 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.
No. Cotlet is independent and not affiliated with Uber or Uber Eats.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy