Food Data Central MCP Server

Created By
jlfwonga year ago
Overview

What is Food Data Central MCP Server?

Food Data Central MCP Server is a Model Context Protocol (MCP) server that provides API access to the USDA's FoodData Central API, allowing users to search for food items and access detailed nutrient information.

How to use Food Data Central MCP Server?

To use the server, clone the repository, install dependencies, and run the server with your USDA API key set as an environment variable. You can also configure it to work with Claude Desktop for easier access.

Key features of Food Data Central MCP Server?

  • Search for foods in the USDA FoodData Central database
  • Access detailed food nutrient information
  • Support for multiple data types (Foundation, SR Legacy, Survey, Branded)
  • Paginated results for efficient data retrieval

Use cases of Food Data Central MCP Server?

  1. Nutritionists can retrieve detailed nutrient profiles for various food items.
  2. Developers can integrate food data into applications for dietary tracking.
  3. Researchers can analyze food composition data for studies.

FAQ from Food Data Central MCP Server?

  • What is the USDA FoodData Central API?

It is a comprehensive food database that provides nutrient information for a wide variety of food items.

  • Is there a cost to use the Food Data Central MCP Server?

No, it is free to use as long as you have a USDA API key.

  • Can I use this server for commercial applications?

Yes, as long as you comply with the USDA's terms of use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jlfwong
Star
1
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

5 hours ago