PlateLens MCP server

PlateLens implements the Model Context Protocol, so an AI assistant can read your nutrition, activity and weight history and reason about it. Every tool is read-only. Access is granted scope by scope over OAuth 2.0 and can be revoked at any time.

MCP endpointhttps://mcp.platelens.app/mcp

Authorization serverhttps://auth.platelens.app

Scopesprofile.read, nutrition.read, activity.read, weight.read, offline_access

Available to every active PlateLens account. Standard OAuth 2.0 with PKCE.

The eight tools

There are eight, and no general-purpose "query my data" tool. A catch-all is a boundary nobody can describe to the person being asked to approve it, so it does not exist here.

Complete v1 capability and data boundary
ToolReadsMaximum rangeScopes
get_profile_targetsGoal, activity level, units, calorie and macro targets, hydration and step goals, stored BMR/TDEE estimate, target weightCurrent stateprofile.read
get_daily_nutrition_summaryOne diary day's nutrition, hydration, health activity, manual exercise, targets and remaining values1 daynutrition.read, profile.read, activity.read
list_mealsCompleted meal summaries with stable IDs, optionally filtered by meal type31 days, 50 per pagenutrition.read
get_mealOne meal: nutrition, effective portion, micronutrients, localized and canonical ingredients1 mealnutrition.read
get_nutrition_trendSelected daily nutrition metrics, averages and current targets90 daysnutrition.read, profile.read
get_activity_summaryDevice activity and manual exercise, kept distinct and also summarized90 daysactivity.read
get_weight_trendWeight and optional body-fat trend, without progress photos or notes365 daysweight.read
get_energy_balanceIntake, estimated expenditure, deficit/surplus, plan adherence and coverageOne named period, anchored to a diary datenutrition.read, activity.read, profile.read

What it cannot do

Connecting

  1. Add a custom connector in your assistant pointing at https://mcp.platelens.app/mcp.
  2. Sign in at auth.platelens.app with the Google or Apple account you use in PlateLens.
  3. Approve the scopes you want. Granting fewer is supported: a connection with only nutrition.read works and simply answers less.

Disconnecting

Either More → Preferences → Connected Apps in the mobile app, or auth.platelens.app in a browser. Each connection is listed and revoked separately; disconnecting an assistant never affects your PlateLens login. Deleting your PlateLens account removes these authorizations as part of the same erasure.

Privacy

The connection API returns an opaque identifier so you can revoke an exact connection; it never returns your account ID, email address, profile, client ID, token or token hash. How PlateLens handles your data is in the privacy policy.

Frequently asked questions

What is the PlateLens MCP server endpoint?

https://mcp.platelens.app/mcp, with OAuth 2.0 authorization at https://auth.platelens.app. It supports PKCE and returns 401 with a WWW-Authenticate resource_metadata pointer for unauthorized requests.

Is the PlateLens MCP server read-only?

Yes. All eight tools are read-only. No tool writes, edits or deletes anything in your account.

Which scopes does it use?

profile.read, nutrition.read, activity.read, weight.read and offline_access. They are approved individually, and granting a subset is supported.

How do I revoke access?

In the app under More → Preferences → Connected Apps, or at auth.platelens.app. Each grant is revoked independently and revocation is enforced on every request, including before a token refresh.

Do I need a paid plan?

No. The MCP server is available to every active PlateLens account. See the pricing page for what the free plan includes.