OpenFoodFacts FAQs

Question 1

Can I use OpenFoodFacts for local development or remote deployment?

Accepted Answer

Yes, OpenFoodFacts supports both. It offers an STDIO mode for local integration (perfect for tools like Claude Desktop) and an HTTP mode for remote deployment as an authenticated API server.

Question 2

How does OpenFoodFacts ensure fast product queries?

Accepted Answer

It achieves speed by utilizing DuckDB for powerful analytical queries on a locally cached, automatically updated Parquet dataset of Open Food Facts product information, optimizing data retrieval and processing.

Question 3

What is OpenFoodFacts and what does it do?

Accepted Answer

OpenFoodFacts is an MCP (Model Context Protocol) server that provides fast, efficient access to the Open Food Facts dataset. It uses DuckDB and Parquet for rapid product queries, enabling developers to integrate food product data into their applications.

Question 4

Is authentication required to use the OpenFoodFacts API?

Accepted Answer

For remote deployments using HTTP mode, a Bearer token is required for all API endpoints except the health check. Local integration via STDIO mode does not require authentication.

Question 5

What types of product information can I search for?

Accepted Answer

The server provides specific tools to search for products by brand and name, and also to find products efficiently using their barcode (UPC/EAN).

OpenFoodFacts

OpenFoodFacts

주요 기능

사용 사례

주요 기능

사용 사례