Uber Eats MCP server
Related Servers
Alternatives to Uber Eats MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceConnects a signed-in account to ChatGPT, Claude and AI agents through Cotlet.dev, enabling users to read cleaning schedules and check-ins, arrange absence cover, review quality reports, and manage stock, with write actions requiring approval by default.7Elastic 2.0
- FlicenseAqualityDmaintenanceAllows AI assistants to browse menus, manage carts, and place orders on Uber Eats through natural language commands.343-
- AlicenseNot gradedqualityCmaintenanceConnects a signed-in Squire barbershop account to AI agents so they can list barbers, services, clients and waitlists, book, reschedule or cancel appointments, block barber time, and pull revenue reports. Write actions on appointments wait for user approval in the Cotlet console, and the same tools are reachable over MCP or a REST API.Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceConnects AI agents to a signed-in contractor account through Cotlet.dev so they can work with estimates, leads, change orders, and job costs. Supports drafting line items, tracking estimate views, reading margins and recorded costs, and reviewing changes before writes are sent.Elastic 2.0
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT, Claude, and other AI agents to manage schedules, routes, customers, quotes, jobs, work orders, invoices, and reports through Cotlet.dev, with approval required for customer- or tech-facing actions.Elastic 2.0
- AlicenseAqualityBmaintenanceEnables ChatGPT, Claude, and other AI agents to access a signed-in restaurant POS account for sales reporting, flagged-bill review, inventory reads, menu management, and approval-gated write actions.7Elastic 2.0
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.