Skip to content

Grok usda mcp server usda_search_foods

How to: Grok usda mcp server usda_search_foods

client:Grok transport:streamable-http tool:usda_search_foods

Add usda mcp server to Grok

  1. 01

    Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "usda-mcp-server": {
      "type": "http",
      "url": "https://usda.caseyjhand.com/mcp"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

    Ask for something usda_search_foods does. Grok lists the server's tools on connect and calls usda_search_foods itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that usda mcp server's identifier in your config matches the one above exactly.

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Set these first

usda mcp server will not start until these are set, so usda_search_foods never becomes available.

  • USDA_FDC_API_KEY
  • MCP_LOG_LEVEL

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.