Open Food Facts MCP Server

Created By
JagjeevanAKa year ago
MCP Server for OpenFoodFacts.
Overview

What is Open Food Facts MCP Server?

The Open Food Facts MCP Server is a Model Context Protocol (MCP) server implementation designed to provide contextual information about food products to AI-powered development tools, enhancing their ability to understand and interact with food-related data.

How to use Open Food Facts MCP Server?

To use the MCP Server, clone the repository, install dependencies, and start the server in either Standard or Developer mode. Users can connect various AI assistants to the server for enhanced functionality.

Key features of Open Food Facts MCP Server?

  • Provides structured access to food product information and code repositories.
  • Supports two operational modes: Standard for general users and Developer for contributors.
  • Offers tools for searching products, analyzing nutritional data, and comparing products.
  • Includes GitHub repository analysis tools in Developer mode.

Use cases of Open Food Facts MCP Server?

  1. Enhancing AI assistance for accurate food product information.
  2. Automating common development tasks for Open Food Facts contributors.
  3. Providing nutritional analysis and recipe suggestions based on food products.
  4. Facilitating better understanding of the codebase for developers.

FAQ from Open Food Facts MCP Server?

  • What is the Model Context Protocol?

The Model Context Protocol is a standardized way for AI tools to communicate with code repositories and data sources, providing structured access to information.

  • How do I start the server?

You can start the server by running npm start for Standard mode or npm start -- --developer for Developer mode after installation.

  • What tools are available in Developer mode?

Developer mode includes tools for GitHub issue analysis, codebase navigation, and more, enhancing the development experience.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JagjeevanAK
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago