Bring Food Delivery
to CrewAI
Create your Vinkius account to connect iFood to CrewAI and start using all 11 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.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the iFood MCP Server?
What you can do
Transform your iFood merchant operations with AI-powered automation. Your agents can:
- Monitor incoming orders in real-time with status tracking
- Accept and progress orders through preparation workflow
- Manage restaurant catalogs — update prices, availability, descriptions
- Review order details including customer info, items, and totals
- Configure operating hours for each day of the week
- Track delivery logistics and assign drivers to orders
- View store information and configuration across all locations
How it works
- Connect your iFood merchant account via JWT token from iFood Developer Portal
- Ask your AI agent to check orders, update menus, or manage schedules
- Natural language commands replace manual app navigation
- Automate repetitive tasks like accepting orders and updating availability
Who is this for?
Essential for restaurant owners, food delivery managers, ghost kitchen operators, and multi-location food businesses using iFood. Let AI agents handle order monitoring, catalog maintenance, and schedule management. Perfect for businesses processing 20+ daily orders who want faster response times, reduced manual oversight, and streamlined operations across multiple store locations.
Built-in capabilities (11)
Requires order ID and driver ID. Use this to manage your own delivery fleet and coordinate order fulfillment. Assign a delivery driver to an iFood order
Use this to review or verify the current schedule before making changes. Get operating hours for an iFood store
Use this to review menu structure, check item availability, or prepare updates to pricing or descriptions. Get the menu catalog for an iFood store
Use this to track order fulfillment and coordinate with delivery personnel. Get logistics/delivery information for an iFood order
Use this to review order contents before accepting or preparing. Get complete details of a specific iFood order
Can filter by status: PENDING, ACCEPTED, PREPARING, READY, DISPATCHED, DELIVERED, CANCELLED. Returns order number, customer info, items, totals, and timestamps. Use this to monitor order flow and track pending orders. List orders for an iFood store
Use this to review store configuration before making updates. Get detailed information about a specific iFood store
Returns store IDs, names, addresses, and operational status. Use this first to get store IDs needed for other operations like fetching orders or managing catalogs. List all stores associated with the iFood merchant account
Requires a schedule object with open/close times for each day. Use this to change store hours, add weekend schedules, or set holiday closures. The schedule should be a JSON object with day keys (monday, tuesday, etc.) and arrays of {start: "HH:MM", end: "HH:MM"} objects. Update operating hours for an iFood store
Only pass the fields you want to change. Common use: update prices, toggle availability, or change descriptions. Requires store ID and item ID. Update a menu item in the iFood store catalog
Common workflow: PENDING -> ACCEPTED -> PREPARING -> READY -> DISPATCHED -> DELIVERED. Can also set to CANCELLED if needed. Use this to progress orders through the fulfillment pipeline. Update the status of an iFood order
Why CrewAI?
When paired with CrewAI, iFood becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call iFood 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
iFood in CrewAI
Why run iFood with Vinkius?
The iFood 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 11 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 iFood using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
iFood and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect iFood 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
iFood for CrewAI
Every request between CrewAI and iFood 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 iFood customers or only merchants?
This MCP server is designed exclusively for iFood merchants (restaurant owners). It uses the Merchant API to manage orders, catalogs, and operations. Consumer-side features require a different API. If you're a restaurant owner using iFood for delivery, this is for you.
Can I accept and prepare orders automatically with this MCP?
Yes! AI agents can update order status through the full workflow: PENDING -> ACCEPTED -> PREPARING -> READY -> DISPATCHED -> DELIVERED. You can build automation rules to accept orders instantly, notify kitchen staff, and track preparation times.
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.
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 →
Haystack (deepset Cloud)
7 toolsBuild and manage AI-powered search and RAG pipelines via deepset Cloud — search documents, run pipelines, and manage workspaces.
Contentstack
10 toolsManage headless CMS via Contentstack — list and create entries, audit content types, handle media assets, and publish to environments directly from any AI agent.
Doppler
12 toolsManage secrets and environment variables via Doppler — list projects, audit secrets, and track activity logs from any AI agent.
Mercury
10 toolsEquip your AI agent with direct access to Mercury — check account balances, review transactions, and manage recipients without opening the banking dashboard.