Bring Food Delivery
to CrewAI
Learn how to connect Deliveroo to CrewAI and start using 5 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Deliveroo MCP Server?
Connect your Deliveroo restaurant account to any AI agent to streamline your kitchen operations and order management through natural language.
What you can do
- Order Lifecycle — List live orders, fetch specific order metadata, and accept or reject incoming requests within the required timeframe.
- Preparation Tracking — Update order stages from 'in_kitchen' to 'ready_for_collection' to keep customers and riders informed in real-time.
- POS Synchronization — Notify Deliveroo of successful or failed POS injections to ensure your tablet and kitchen systems stay perfectly in sync.
- Operational Insights — Query historical orders by brand, restaurant, or date range to analyze performance without leaving your workspace.
How it works
- Subscribe to this server
- Enter your Deliveroo API Client ID and Secret
- Start managing your restaurant flow from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Restaurant Managers — monitor live order flows and update kitchen statuses without juggling multiple tablets.
- Operations Teams — audit order history and sync failures across multiple brands or locations.
- Developers — integrate delivery workflows into internal tools or custom dashboards using natural language queries.
Built-in capabilities (5)
Inform Deliveroo of order preparation progress
Notify Deliveroo of POS injection status
Get details for a single Deliveroo order
List Deliveroo orders
Must be called within ~10 minutes of receiving a new order. Accept, reject, or confirm a Deliveroo order
Why CrewAI?
When paired with CrewAI, Deliveroo becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Deliveroo 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
Deliveroo in CrewAI
Deliveroo and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Deliveroo to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Deliveroo in CrewAI
The Deliveroo 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. All 5 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Deliveroo for CrewAI
Every tool call from CrewAI to the Deliveroo MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I reject an order if an ingredient is unavailable?
Yes. Use the update_order_status tool with the status 'rejected' and provide 'ingredient_unavailable' as the reason.
How do I notify the rider that the food is ready for collection?
You can use the create_prep_stage tool and set the stage to 'ready_for_collection'. This updates both Deliveroo and the rider.
Is it possible to see only the orders that are currently active?
Yes, use the get_orders tool and set the live_orders parameter to true to filter for ongoing deliveries.
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 →
EasyPractice
10 toolsEquip your AI agent to manage clinic appointments, track clients, and monitor invoices via the EasyPractice API.
Oura
7 toolsAccess your Oura Ring health data — sleep, activity, readiness, HRV, heart rate and workout metrics from any AI agent.
Zoho Campaign
13 toolsAI email marketing: manage campaigns, contacts, and mailing lists via agents.
Linear
12 toolsStreamline issue tracking and project management via Linear — list teams, query issues, create comments and inspect cycles directly from any AI agent.