Portal
SandboxAPI v1Not signed inExternal user: —

MCP

Expose FoodAPI capabilities to AI hosts through a public MCP facade — same intelligence as REST, scoped with OAuth.

What you can build

Cooking assistants in Cursor/Claude, pantry agents, meal planners, and nutrition lookup tools — without embedding developer API keys in the client.

Shortest path

  1. Create an MCP application in the portal.
  2. Point your MCP client at https://mcp.foodapi.dev/apps/{public_id}/mcp.
  3. Complete OAuth and call a tool such as get_nutrition.
MCP quickstart →

Identity (do not confuse these)

  • Developer API key — trusted server REST/SDK only
  • MCP application — OAuth client you register
  • End-user grant — scopes over that user's partition

Never put developer API keys in browser or mobile MCP configs. MCP authentication

Public tools (examples)

get_nutrition · search_recipes · analyze_recipe · review_pantry
plan_meals · check_dietary_compatibility · transform_recipe
save_recipe · update_pantry · manage_pending_writes · …

Full list and write-safety: Tools · Scopes

Next

Configure a client and make your first tool call.

Continue to MCP quickstart →