Localplate Mcp
Give your coding agent verified restaurant nutrition, food search, and diary tooling when you are building or dogfooding a health or food-tracking product.
Overview
LocalPlate MCP is a MCP server for the Build phase that exposes verified restaurant nutrition, food search, diary logs, and Plato guidance to your agent over streamable HTTP.
What is this MCP server?
- Streamable-HTTP remote MCP at Supabase edge—no local npm server package in the registry manifest
- Verified restaurant nutrition data for agent-driven meal and menu questions
- Food search plus diary logging flows for habit and compliance-style apps
- Plato guidance tooling for coaching-style nutrition prompts in the agent
- Version 1.0.0 catalog entry aligned to the official server.schema.json remote definition
- Server version 1.0.0 in catalog manifest
- Single streamable-http remote endpoint (no npm stdio package listed)
- Four capability areas named in description: nutrition, search, diary, Plato guidance
What problem does it solve?
Agents hallucinate calories and chain menus unless you plug in a verified nutrition and logging backend.
Who is it for?
Indie builders adding restaurant-accurate nutrition or diary features to agent-first mobile or SaaS prototypes.
Skip if: Teams that only need generic recipe blogs scraped from the web without verified restaurant data.
What do I get? / Deliverables
After you register the remote endpoint, your agent can query verified foods, log diary entries, and apply Plato guidance inside the same thread.
- Agent-callable food search and nutrition tools
- Diary logging actions wired into your assistant
- Plato guidance prompts backed by the LocalPlate service
Recommended MCP Servers
Journey fit
Nutrition and diary APIs are wired in during product build when the agent needs live food data, not during pure ideation. integrations is the canonical shelf because LocalPlate is an external MCP service (streamable HTTP) you register so agents can call food search and logging tools.
How it compares
Remote nutrition-data MCP, not a local repo-memory or web-scrape utility.
Common Questions / FAQ
Who is LocalPlate MCP for?
Solo and indie developers building health, fitness, or food-logging products who want agents to use verified restaurant nutrition instead of guessing macros.
When should I use LocalPlate MCP?
Use it when you are integrating meal search, diary logging, or coaching prompts into Claude Code or Cursor during build or early grow experiments.
How do I add LocalPlate MCP to my agent?
Add the published streamable-http remote URL from the server manifest to your MCP client configuration and restart the agent so the nutrition and diary tools load.