2,500+ MCP servers ready to use
Vinkius

iFood MCP Server for Cline 11 tools — connect in under 2 minutes

Built by Vinkius GDPR 11 Tools IDE

Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire iFood through Vinkius and Cline gains direct access to every tool. from data retrieval to workflow automation. without leaving the terminal.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install iFood and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "ifood": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
iFood
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 iFood MCP Server

What you can do

Transform your iFood merchant operations with AI-powered automation. Your agents can:

Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including iFood tool calls without waiting for prompts between steps. Connect 11 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.

  • 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

The iFood MCP Server exposes 11 tools through the Vinkius. Connect it to Cline 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 iFood to Cline via MCP

Follow these steps to integrate the iFood MCP Server with Cline.

01

Open Cline MCP Settings

Click the MCP Servers icon in the Cline sidebar panel

02

Add remote server

Click "Add MCP Server" and paste the configuration above

03

Enable the server

Toggle the server switch to ON

04

Start using iFood

Ask Cline: "Using iFood, help me...". 11 tools available

Why Use Cline with the iFood MCP Server

Cline provides unique advantages when paired with iFood through the Model Context Protocol.

01

Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts

02

Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window

03

Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation

04

Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing

iFood + Cline Use Cases

Practical scenarios where Cline combined with the iFood MCP Server delivers measurable value.

01

Autonomous feature building: tell Cline to fetch data from iFood and scaffold a complete module with types, handlers, and tests

02

Codebase refactoring: use iFood tools to validate live data while Cline restructures your code to match updated schemas

03

Automated testing: Cline fetches real responses from iFood and generates snapshot tests or mocks based on actual payloads

04

Incident response: query iFood for real-time status and let Cline generate hotfix patches based on the findings

iFood MCP Tools for Cline (11)

These 11 tools become available when you connect iFood to Cline via MCP:

01

assign_driver

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

02

get_business_hours

Use this to review or verify the current schedule before making changes. Get operating hours for an iFood store

03

get_catalog

Use this to review menu structure, check item availability, or prepare updates to pricing or descriptions. Get the menu catalog for an iFood store

04

get_logistics

Use this to track order fulfillment and coordinate with delivery personnel. Get logistics/delivery information for an iFood order

05

get_order_details

Use this to review order contents before accepting or preparing. Get complete details of a specific iFood order

06

get_orders

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

07

get_store_details

Use this to review store configuration before making updates. Get detailed information about a specific iFood store

08

get_stores

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

09

update_business_hours

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

10

update_catalog_item

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

11

update_order_status

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

Example Prompts for iFood in Cline

Ready-to-use prompts you can give your Cline agent to start working with iFood immediately.

01

"Show me all pending orders and accept them automatically"

02

"Update the price of 'Combo Burger Especial' to R$32.90 and mark it as unavailable until tomorrow"

03

"Change my store hours to open at 11am and close at 11pm every day this week"

Troubleshooting iFood MCP Server with Cline

Common issues when connecting iFood to Cline through the Vinkius, and how to resolve them.

01

Server shows error in sidebar

Click the server name to see logs. Verify the URL and token are correct.

iFood + Cline FAQ

Common questions about integrating iFood MCP Server with Cline.

01

How does Cline connect to MCP servers?

Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
02

Can Cline run MCP tools without approval?

By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
03

Does Cline support multiple MCP servers at once?

Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.

Connect iFood to Cline

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