2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 14 Tools SDK

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add Uber Eats as an MCP tool provider through the Vinkius and your ADK agents can call every tool with full schema introspection.

Vinkius supports streamable HTTP and SSE.

python
from google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token — get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="uber_eats_agent",
    instruction=(
        "You help users interact with Uber Eats "
        "using 14 available tools."
    ),
    tools=[mcp_tools],
)
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:

Google ADK natively supports Uber Eats as an MCP tool provider — declare the Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 14 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

  • 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 Google ADK 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 Google ADK via MCP

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

01

Install Google ADK

Run pip install google-adk

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Create the agent

Save the code above and integrate into your ADK workflow

04

Explore tools

The agent will discover 14 tools from Uber Eats via MCP

Why Use Google ADK with the Uber Eats MCP Server

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

01

Google ADK natively supports MCP tool servers — declare a tool provider and the framework handles discovery, validation, and execution

02

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with Uber Eats

03

Production-ready features like session management, evaluation, and deployment come built-in — not bolted on

04

Seamless integration with Google Cloud services means you can combine Uber Eats tools with BigQuery, Vertex AI, and Cloud Functions

Uber Eats + Google ADK Use Cases

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

01

Enterprise data agents: ADK agents query Uber Eats and cross-reference results with internal databases for comprehensive analysis

02

Multi-modal workflows: combine Uber Eats tool responses with Gemini's vision and language capabilities in a single agent

03

Automated compliance checks: schedule ADK agents to query Uber Eats regularly and flag policy violations or configuration drift

04

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including Uber Eats

Uber Eats MCP Tools for Google ADK (14)

These 14 tools become available when you connect Uber Eats to Google ADK 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 Google ADK

Ready-to-use prompts you can give your Google ADK 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 Google ADK

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

01

McpToolset not found

Update: pip install --upgrade google-adk

Uber Eats + Google ADK FAQ

Common questions about integrating Uber Eats MCP Server with Google ADK.

01

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.
02

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.
03

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.

Connect Uber Eats to Google ADK

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