2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 11 Tools CLI

Claude Code is Anthropic's agentic CLI for terminal-first development. Add iFood as an MCP server in one command and Claude Code will discover every tool at runtime — ideal for automation pipelines, CI/CD integration, and headless workflows via the Vinkius.

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·bash
# Your Vinkius token — get it at cloud.vinkius.com
claude mcp add ifood --transport http "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:

Claude Code registers iFood as an MCP server in a single terminal command. Once connected, Claude Code discovers all 11 tools at runtime and can call them headlessly — ideal for CI/CD pipelines, cron jobs, and automated workflows where iFood data drives decisions without human intervention.

  • 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 Code 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 Code via MCP

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

01

Install Claude Code

Run npm install -g @anthropic-ai/claude-code if not already installed

02

Add the MCP Server

Run the command above in your terminal

03

Verify the connection

Run claude mcp to list connected servers, or type /mcp inside a session

04

Start using iFood

Ask Claude: "Using iFood, show me..."11 tools are ready

Why Use Claude Code with the iFood MCP Server

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

01

Single-command setup: `claude mcp add` registers the server instantly — no config files to edit or applications to restart

02

Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

03

Claude Code runs headlessly, enabling unattended batch processing using iFood tools in cron jobs or deployment scripts

04

Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

iFood + Claude Code Use Cases

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

01

CI/CD integration: embed iFood tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping

02

Headless batch processing: schedule Claude Code to query iFood nightly and generate reports without human intervention

03

Shell scripting: pipe iFood outputs into other CLI tools for data transformation, filtering, and aggregation

04

Infrastructure monitoring: run Claude Code in a cron job to query iFood status endpoints and alert on anomalies

iFood MCP Tools for Claude Code (11)

These 11 tools become available when you connect iFood to Claude Code 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 Claude Code

Ready-to-use prompts you can give your Claude Code 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 Claude Code

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

01

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
02

Connection timeout

Check your internet connection and verify the Edge URL is reachable

iFood + Claude Code FAQ

Common questions about integrating iFood MCP Server with Claude Code.

01

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
02

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
03

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

Connect iFood to Claude Code

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