Bring Order Management
to CrewAI
Create your Vinkius account to connect Uber Eats to CrewAI and start using all 14 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
Compatible with every major AI agent and IDE
What is the Uber Eats MCP Server?
What you can do
Connect AI agents to the Uber Eats Marketplace API for complete restaurant and delivery management:
- 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
How it works
- Connect your Uber Eats merchant account via OAuth token from Uber Developer Portal
- Ask your AI agent to check orders, update menus, track deliveries, or manage stores
- Natural language commands replace manual Uber Eats Manager app navigation
- Automate repetitive tasks like accepting orders, updating availability, and tracking deliveries
Who is this for?
Essential for restaurant owners, food delivery managers, multi-location food businesses, ghost kitchen operators, franchise managers, and POS system integrators using Uber Eats. Let AI agents handle order monitoring, menu maintenance, delivery tracking, and store management. Perfect for businesses processing 20+ daily orders who want faster response times, reduced manual oversight, and streamlined operations across multiple restaurant locations.
Built-in capabilities (14)
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
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
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)
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
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
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
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
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
Use this to review store configuration, verify delivery settings, or check operational status. Get detailed information about a specific Uber Eats restaurant/store
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
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
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)
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
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)
Why CrewAI?
When paired with CrewAI, Uber Eats becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Uber Eats tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Uber Eats in CrewAI
Why run Uber Eats with Vinkius?
The Uber Eats connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 14 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.




Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Uber Eats using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Uber Eats and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Uber Eats to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Uber Eats for CrewAI
Every request between CrewAI and Uber Eats is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
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.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Clientjoy
8 toolsManage agency CRM and invoicing via Clientjoy — track leads, monitor invoices, and manage client projects directly from any AI agent.

Baidu Translate / 百度翻译
10 toolsChina's leading machine translation service — translate text and detect languages via AI.

Expensya
12 toolsSubmit and approve business expenses in seconds with receipt scanning, policy enforcement, and reimbursement workflows.

John Deere
7 toolsMonitor farm operations via John Deere APIs — track machines, map fields, review planting and harvest data from any AI agent.
