2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 14 Tools IDE

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Uber Eats through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "uber-eats": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Uber Eats
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:

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Uber Eats tool calls without waiting for prompts between steps. Connect 14 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

  • 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 Cline 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 Cline via MCP

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

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel

02

Add remote server

Click "Add MCP Server" and paste the configuration above

03

Enable the server

Toggle the server switch to ON

04

Start using Uber Eats

Ask Cline: "Using Uber Eats, help me...". 14 tools available

Why Use Cline with the Uber Eats MCP Server

Cline provides unique advantages when paired with Uber Eats through the Model Context Protocol.

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

Uber Eats + Cline Use Cases

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

01

Autonomous feature building: tell Cline to fetch data from Uber Eats and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use Uber Eats tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from Uber Eats and generates snapshot tests or mocks based on actual payloads

04

Incident response: query Uber Eats for real-time status and let Cline generate hotfix patches based on the findings

Uber Eats MCP Tools for Cline (14)

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

01

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

02

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

03

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)

04

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

05

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

06

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

07

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

08

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

09

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

10

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

11

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

12

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)

13

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

14

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 Cline

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

01

"Show me all pending orders and accept them automatically"

02

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

03

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

Troubleshooting Uber Eats MCP Server with Cline

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

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

Uber Eats + Cline FAQ

Common questions about integrating Uber Eats MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Connect Uber Eats to Cline

Get your token, paste the configuration, and start using 14 tools in under 2 minutes. No API key management needed.