
Localplate Mcp
io.github.Daniel-ChernyPublished by GitHub account Daniel-Chernyv1.0.0Updated Oct 25, 2026
LocalPlate MCP for verified restaurant nutrition, food search, diary logs, and Plato guidance.
Overview
LocalPlate MCP gives an assistant verified restaurant nutrition data, food search, diary logging and Plato guidance through a remote OAuth-protected endpoint.
- What you can do
- Search foods and restaurant menu items for verified nutrition information, such as calories and other nutrient values, to compare options or answer diet questions. Log and review diary entries so an assistant can track what was eaten over time. Provide Plato guidance, presumably advice or recommendations drawn from the service. The manifest lists no individual tools, so the exact operations and their inputs are not documented here.
- When to use it
- Useful when someone wants an assistant to look up restaurant nutrition, search foods, keep a food diary, or get guidance from the LocalPlate service, rather than general web nutrition lookups.
- Requirements
- A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. Authentication is required and uses OAuth, so the user must sign in to a LocalPlate account through the OAuth flow. Network access to the hosted endpoint is needed.
Installation
In SourceWeft
- Open Localplate Mcp in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Daniel-Cherny%2Flocalplate-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"localplate": {
"type": "http",
"url": "https://iihzbnyxbxhsrexqsori.supabase.co/functions/v1/localplate-mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.