How to Use the iFood MCP in CrewAI

Q: Can I limit which iFood tools a specific CrewAI agent can use?

Yes. You can filter the tools so your menu agent only gets getcatalog and updatecatalogitem, while blocking it from dispatch tools.

Deploy a crew of specialized CrewAI agents to manage your iFood MCP Server operations autonomously.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect iFood MCP to CrewAI

Create your Vinkius account to connect iFood to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup iFood with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Agent Teams for iFood MCP Server

CrewAI lets you split up operational tasks among specialized agents. A Triage Agent can constantly monitor `get_orders`, while a Prep Agent uses `get_order_details` to coordinate with the kitchen. This team setup ensures no order gets lost. The agents share memory, passing order details smoothly before calling `update_order_status` to move the ticket to the preparation phase.

Autonomous Menu and Catalog Auditing

Keep your digital storefront accurate without manual spot checks. An Auditor Agent runs `get_catalog` to pull your menu, while an Analyst Agent compares prices against your POS data. If a discrepancy is found, the agent uses `update_catalog_item` to correct the price or description. This keeps your listings accurate across all locations returned by `get_stores`.

Fleet Coordination and Dispatching via CrewAI

Coordinate your delivery fleet without lifting a finger. A Dispatch Agent monitors logistics via `get_logistics` to find delayed orders, while a Fleet Agent matches drivers using `assign_driver`. They work in tandem, checking `get_store_details` to verify pickup spots. This continuous coordination loop ensures orders are dispatched efficiently, updating the final status to ready.

Setup guide

Set up iFood MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke iFood tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="iFood Analyst",
    goal="Access and analyze iFood data via MCP.",
    backstory="Expert analyst with direct iFood access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent iFood transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="iFood Analyst",
        goal="Access and analyze iFood data via MCP.",
        backstory="Expert analyst with direct iFood access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent iFood transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by iFood. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect iFood now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about iFood MCP in CrewAI

CrewAI's shared memory allows one agent to fetch order details using `get_order_details` and pass that context directly to another agent responsible for driver dispatch.

Yes. You can filter the tools so your menu agent only gets `get_catalog` and `update_catalog_item`, while blocking it from dispatch tools.

You pass the secure Vinkius endpoint URL directly into the agent's parameters. The crew will automatically discover tools like `get_orders` and start collaborating.

The agent handles the error based on its role definition, either retrying the call to `get_logistics` or escalating the issue to a supervisor agent.

All data, including customer names and delivery coordinates from `get_orders`, is processed within Vinkius's zero-trust sandboxes, ensuring zero persistence after the tool run completes.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript