PlateLens MCP server
PlateLens implements the Model Context Protocol, so an AI assistant can read your nutrition, activity, weight and glucose 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 endpoint — https://mcp.platelens.app/mcp
Authorization server — https://auth.platelens.app
Scopes — profile.read, nutrition.read, activity.read, weight.read, glucose.read, offline_access
Available to every active PlateLens account. Standard OAuth 2.0 with PKCE.
The nine tools
There are nine, 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.
| Tool | Reads | Maximum range | Scopes |
|---|---|---|---|
get_profile_targets | Goal, activity level, units, calorie and macro targets, hydration and step goals, stored BMR/TDEE estimate, target weight | Current state | profile.read |
get_daily_nutrition_summary | One diary day's nutrition, hydration, health activity, manual exercise, targets and remaining values | 1 day | nutrition.read, profile.read, activity.read |
list_meals | Completed meal summaries with stable IDs, optionally filtered by meal type | 31 days, 50 per page | nutrition.read |
get_meal | One meal: nutrition, effective portion, micronutrients, localized and canonical ingredients | 1 meal | nutrition.read |
get_nutrition_trend | Selected daily nutrition metrics, averages and current targets | 90 days | nutrition.read, profile.read |
get_activity_summary | Device activity and manual exercise, kept distinct and also summarized | 90 days | activity.read |
get_weight_trend | Weight and optional body-fat trend, without progress photos or notes | 365 days | weight.read |
get_energy_balance | Intake, estimated expenditure, deficit/surplus, plan adherence and coverage | One named period, anchored to a diary date | nutrition.read, activity.read, profile.read |
list_glucose_readings | Stored glucose values in mmol/L, observation times and recorded time context, source platform and reported measurement method; no notes or provider identifiers | 31 days, 100 per page | glucose.read |
Glucose access
Glucose requires its own explicit glucose.read approval. An existing connection does not gain this permission automatically: reconnect and select it if you want to share glucose. The assistant reads only observations already recorded or synced to PlateLens. It cannot request Apple Health or Health Connect permission, start a sync, provide monitoring or alarms, or change a reading.
Each request covers at most 31 days and returns up to 100 observations per page. Values retain their stored mmol/L precision and measurement-time context; missing readings remain missing. This tool provides recorded observations without clinical targets or diagnoses. See glucose connection instructions.
What it cannot do
- No writes. An assistant cannot log a meal, edit an entry, change a target or delete anything.
- No photos, no notes. Meal photos and progress photos are not exposed, and the weight tool returns the trend without its notes.
- No more than you granted. Nutrition, activity, weight, glucose and profile are separate scopes, approved individually.
- No survival past revocation. Revocation is checked on every request, including before any token refresh.
Connecting
- Add a custom connector in your assistant pointing at
https://mcp.platelens.app/mcp. - Sign in at auth.platelens.app with the Google or Apple account you use in PlateLens.
- Approve the scopes you want. Granting fewer is supported: a connection with only
nutrition.readworks 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 nine 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, glucose.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.