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.

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

Name: iFood
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 11 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

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.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "ifood": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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:

Claude Desktop is the definitive way to connect iFood to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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 Claude Desktop 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 Claude Desktop via MCP

Follow these steps to integrate the iFood MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using iFood

Look for the 🔌 icon in the chat — your 11 tools are now available

Why Use Claude Desktop with the iFood MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with iFood through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

iFood + Claude Desktop Use Cases

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

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

iFood MCP Tools for Claude Desktop (11)

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

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

get_business_hours

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

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

get_logistics

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

get_order_details

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

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

get_store_details

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

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

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

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

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 Claude Desktop

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

"Show me all pending orders and accept them automatically"

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

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

Troubleshooting iFood MCP Server with Claude Desktop

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

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

iFood + Claude Desktop FAQ

Common questions about integrating iFood MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.