Uber Eats MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Used to authenticate the MCP connection (e.g. as a Bearer token) or passed as an environment variable when running the local stdio bridge. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Uber Eats through Cotlet.dev. Call uber_eats_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| uber_eats_guideA | How to work in Uber Eats (stores, menus, hours and orders): its screens and the sign-in link. Call this first. |
| uber_eats_statusB | Check that your Cotlet.dev account and Uber Eats are ready: account, credits and Uber Eats connection. |
| uber_eats_openB | Open a Uber Eats page in your signed-in Cloud Browser (default https://merchants.ubereats.com) to work with stores, menus, hours and orders. |
| uber_eats_readB | Read the current Uber Eats page: its text and numbered buttons, links and fields. |
| uber_eats_clickB | Click a numbered element on the current Uber Eats page. |
| uber_eats_typeB | Type text into a numbered field on the current Uber Eats page. |
| uber_eats_closeA | Close the Uber Eats browser session when the work is done, so credits stop running. |
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 7 tools
Each tool maps to a single, clearly distinct browser-automation primitive (open, read, click, type, close) plus setup (guide, status). The descriptions explicitly disambiguate ordering ('call this first') and targets, so there is essentially no chance of misselection.
All seven tools follow a uniform snake_case pattern with the shared uber_eats_ prefix and a single verb/noun token (uber_eats_open, uber_eats_read, uber_eats_click). The convention is predictable and consistent throughout.
Seven tools is well-scoped for a browser-driving server: a guide, a status check, and the minimal primitive set needed to operate a page. Nothing feels padded or missing at the tool level.
The open/read/click/type/close loop covers the core interaction lifecycle for merchants.ubereats.com, and a guide plus status tool handles onboarding. Minor gaps exist (no explicit navigate-to-URL, scroll, back, or screenshot/wait primitive), which an agent can partially work around via read and clicking numbered links.