Open Food Facts logo

Open Food Facts

Search, inspect, and contribute Open Food Facts product data through MCP tools.

Install Open Food Facts

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "open-food-facts": {
      "command": "npx",
      "args": [
        "-y",
        "openfoodfacts-mcp"
      ],
      "env": {
        "OFF_USER_AGENT": "YOUR_VALUE_HERE",
        "OFF_USER_ID": "YOUR_VALUE_HERE",
        "OFF_PASSWORD": "YOUR_VALUE_HERE",
        "OFF_COUNTRY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 10 tools correctly ().

Overview

The Open Food Facts MCP server connects MCP clients to the Open Food Facts API for product lookup, search, and contributions. It supports barcode queries, structured filters, Lucene search, autocomplete, product edits, image handling, and direct API calls. Set a user agent for API access; write operations additionally require Open Food Facts credentials. Use it when an agent needs food product information or needs to add and update database records.

Use cases

  • Look up nutrition data by product barcode
  • Search products by brand, category, or Nutri-Score
  • Explore brands and labels with autocomplete
  • Add or update product records
  • Upload and adjust product images

Key features

  • Barcode product lookup
  • Structured product search
  • Lucene query support
  • Product and image contributions
  • Direct Open Food Facts API access
  • API documentation lookup

Tools10

What Open Food Facts lets your agent do. Expand a tool for its parameters.

Verified live~6.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

9/9 checks healthy over the last 55d

What it can do

From the 10 tools this server returned when we ran it; 10 declare their own safety hints.

Runs commands · 1Handles credentials · 1Read-only tools · 9
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age252 days
Maintainers1

Observed 2026-10-28 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · openfoodfacts-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads957Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed10Callable tools this server registers over MCP.

How Open Food Facts works

What Open Food Facts MCP server does

The Open Food Facts MCP server gives an MCP client access to product data from the Open Food Facts database and API. It supports both read and write workflows, so an agent can inspect an existing item, search across products, or contribute product details when authenticated.

Typical read tasks include finding a product from its barcode, retrieving nutrition information, locating products by brand or category, and filtering by Nutri-Score. The server can also help explore database vocabulary by suggesting brands, categories, labels, and similar values.

Write workflows can create or update a product, upload a product image, and select, crop, or rotate an image. These operations modify Open Food Facts data and should be used with the required account credentials.

How it works

The Open Food Facts MCP server exposes the Open Food Facts API through MCP tools. A client sends a tool request, and the server performs the corresponding database or API operation. Product lookup uses a barcode, while standard search accepts structured filters such as brand, category, and Nutri-Score.

For more advanced queries, Lucene search supports syntax including negation and boolean logic. The call_api tool provides a lower-level way to reach Open Food Facts API endpoints directly, and get_api_docs returns API documentation for discovering endpoint details.

This server fits assistants that need food catalog data during conversations, product research, nutrition lookups, or data contribution tasks. It is less suitable when an application requires a separate private product database or capabilities not exposed by the Open Food Facts API.

Setup and configuration

Configure the server in an MCP client using the installation instructions linked by the project. The referenced setup flow generates client configuration and lists support for Claude Code, Claude Desktop, Cursor, Cline, VS Code, and other clients.

OFF_USER_AGENT is required. Set it to an identifying value for the application, such as an application name, version, and contact address. The server uses the world country subdomain by default; set OFF_COUNTRY to select another country subdomain.

Read-only tools do not require an Open Food Facts account. To add or edit products or upload images, set both OFF_USER_ID and OFF_PASSWORD. The authentication requirement for call_api depends on the endpoint being called.

Tools and capabilities

  • get_product: Retrieves product information by barcode.
  • search_products_standard: Searches with structured brand, category, and Nutri-Score filters.
  • search_products_lucene: Runs Lucene queries with boolean logic and negation.
  • autocomplete: Suggests brands, categories, labels, and other database terms.
  • add_or_edit_product: Creates or updates a product record.
  • upload_image: Uploads a product image.
  • select_image: Selects, crops, and rotates an image.
  • call_api: Calls an Open Food Facts API endpoint directly.
  • get_api_docs: Retrieves Open Food Facts API documentation.

Limitations and notes

Write tools need Open Food Facts credentials, while read tools do not. Direct API calls may also require authentication depending on the selected endpoint. The server depends on the data and endpoint behavior provided by Open Food Facts, and its country context defaults to the world subdomain unless configured otherwise.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Open Food Facts

Open Food Facts is an MCP server that connects AI clients to the Open Food Facts database and API. It provides product lookup, structured and Lucene search, autocomplete, product editing, image upload, image selection, direct API calls, and API documentation. Write operations require Open Food Facts credentials.

Use the project's install-mcp instructions to generate configuration for your MCP client. The documented setup supports Claude Code, Claude Desktop, Cursor, Cline, VS Code, and other clients. Set the required environment variables before starting the server.

Read-only access requires `OFF_USER_AGENT`. Product edits and image uploads additionally require `OFF_USER_ID` and `OFF_PASSWORD`. Authentication for direct API calls depends on the Open Food Facts endpoint being used.

Yes, `search_products_standard` supports Nutri-Score filters along with structured brand and category filters. Use it to search for products such as breakfast cereals with a selected nutrition grade.

Yes, it provides `upload_image` for image uploads and `select_image` for selecting, cropping, and rotating an image. Image contribution workflows require Open Food Facts credentials.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpen Food Facts AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/open-food-facts?style=directory)](https://allmcps.com/mcp/open-food-facts)
HTML Embed
<a href="https://allmcps.com/mcp/open-food-facts"><img src="https://allmcps.com/api/badge/open-food-facts?style=directory" alt="Open Food Facts on AllMCPs" /></a>