Does this work for Uber Eats customers or only merchants?

This MCP server is designed exclusively for Uber Eats merchants (restaurant owners). It uses the Uber Eats Marketplace API to manage orders, menus, deliveries, and store operations. Consumer-side features (browsing restaurants, placing orders) require the Uber consumer app. If you're a restaurant owner using Uber Eats for delivery, this is for you.

Can I automatically accept all incoming orders?

Yes! AI agents can monitor pending orders and auto-accept them based on your criteria. You can set up automation rules to accept orders instantly during business hours, reject when kitchen is at capacity, or flag special instructions for manual review. This significantly reduces response times and improves restaurant ratings on the platform.

Does this support multiple restaurant locations?

Absolutely. The API returns all stores associated with your merchant account. Each tool requires a store_id parameter, so you can manage operations independently across all your restaurant locations. AI agents can list all your stores first to get their IDs, then manage menus, orders, and settings for each location separately.

Uber Eats MCP Server for Claude Desktop 14 tools — connect in under 2 minutes

Name: Uber Eats
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 14 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Uber Eats and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "uber-eats": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Uber Eats MCP Server

What you can do

Connect AI agents to the Uber Eats Marketplace API for complete restaurant and delivery management:

Claude Desktop is the definitive way to connect Uber Eats to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 14 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

Monitor incoming orders in real-time with status tracking (PENDING → ACCEPTED → PREPARING → READY → DELIVERED)
Accept or reject orders instantly based on kitchen capacity
Manage restaurant menus — update prices, availability, descriptions, dietary tags
Review order details including customer info, items, special instructions, and totals
Track delivery status with real-time courier GPS location and ETA
Handle order issues including customer complaints and refund requests
View store information and configuration across all registered locations
Mark orders ready for courier pickup when food is prepared

The Uber Eats MCP Server exposes 14 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Uber Eats to Claude Desktop via MCP

Follow these steps to integrate the Uber Eats MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Uber Eats

Look for the 🔌 icon in the chat — your 14 tools are now available

Why Use Claude Desktop with the Uber Eats MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Uber Eats through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Uber Eats + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Uber Eats MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Uber Eats MCP Tools for Claude Desktop (14)

These 14 tools become available when you connect Uber Eats to Claude Desktop via MCP:

accept_order

This notifies the customer that the restaurant is preparing their food and triggers courier assignment by Uber Eats. Required before marking order as ready for pickup. Use this to acknowledge incoming orders and begin food preparation. Should be done promptly to maintain good restaurant ratings. Accept a pending Uber Eats order to confirm preparation

cancel_order

This is different from rejection - cancellation happens after acceptance and may result in customer dissatisfaction and potential platform penalties. Requires a cancellation reason. Use only when absolutely necessary (kitchen emergency, safety issue, or unavoidable circumstance). Cancel an already accepted Uber Eats order

complete_order

This should be called after confirmation that the delivery was successful. Closes the order lifecycle and triggers final payment processing. Use this to confirm order completion. Mark an order as fully completed (delivered and finalized)

get_delivery_status

Use this to track delivery progress, answer customer inquiries about their order, or coordinate with couriers. Get real-time delivery tracking status for an Uber Eats order

get_menus

Use this to review menu structure, check which items are available/out of stock, or get menu item IDs needed for availability updates. Get complete menu catalog for a specific Uber Eats restaurant

get_order

Use this to review order contents before accepting, verify special instructions, or prepare items correctly. Get complete details of a specific Uber Eats delivery order

get_order_issues

Returns issue descriptions, timestamps, resolution status, and any refunds issued. Use this to review and address order problems, improve quality, and handle disputes proactively. Get reported issues and complaints for a specific Uber Eats order

get_orders

Can filter by status: PENDING (awaiting restaurant acceptance), ACCEPTED (restaurant confirmed), PREPARING (food being prepared), READY (ready for courier pickup), DELIVERED (completed), CANCELLED, or REJECTED. Returns order IDs, customer info, items ordered, totals, special instructions, and timestamps. Use this to monitor order flow, track pending orders requiring action, or review completed deliveries. List all orders for your Uber Eats restaurants with optional status filter

get_store

Use this to review store configuration, verify delivery settings, or check operational status. Get detailed information about a specific Uber Eats restaurant/store

get_stores

Returns external store IDs, names, addresses, operating status, and business details. Use this tool first to get your store IDs, which are required for all other menu and order management operations. List all restaurants/stores associated with your Uber Eats merchant account

mark_order_prep_started

Updates order status to PREPARING and notifies the customer. Use this to keep customers informed about their order progress and provide accurate delivery time estimates. Mark that food preparation has started for an accepted order

mark_order_ready

This triggers courier dispatch notification. Use this when food is complete and waiting for courier arrival. Couriers will be routed to your location for pickup. Mark order as ready for courier pickup (food is packaged and waiting)

reject_order

The customer is notified and refunded automatically. Provide a reason code: "item_unavailable" (key ingredients out of stock), "too_busy" (kitchen at capacity), "kitchen_closed" (outside operating hours), or "other". Use this when unable to fulfill an order. Excessive rejections may affect restaurant visibility on the platform. Reject a pending Uber Eats order when unable to fulfill it

update_menu_item_availability

Set available=true to mark item as in-stock and orderable, or available=false to mark as out-of-stock. Common use: quickly mark items as unavailable when ingredients run out, then re-enable when restocked. Requires external store ID and menu item ID from get_menus result. Toggle availability status of a menu item (mark as in-stock or out-of-stock)

Example Prompts for Uber Eats in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Uber Eats immediately.

"Show me all pending orders and accept them automatically"

"Update the price of 'Margherita Pizza' to R$45.90 and mark it as unavailable"

"Track the delivery status of order #12345 and tell me where the courier is"

Troubleshooting Uber Eats MCP Server with Claude Desktop

Common issues when connecting Uber Eats to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Uber Eats + Claude Desktop FAQ

Common questions about integrating Uber Eats MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.