Ask Claude, ChatGPT or Cursor about your Apple Health data: workouts, sleep, food. Read-only.
Connect Remote server
claude mcp add --transport http metrics-nest https://api.metricsnest.app/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"metrics-nest": {
"url": "https://api.metricsnest.app/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"metrics-nest": {
"type": "http",
"url": "https://api.metricsnest.app/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.metricsnest.app/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 26 found in our last check
get_profileThe account behind this key: its plan, the days this key may read (meta.history_floor and history_ceiling, null when open), the categories this key may read, the paired devices and when each last synced, the account time zone, and when this share expires (expires_at: past it, ev…
list_metricsEvery metric there is a figure for, with its unit and the first and last day. Use the exact metric names from here in query_metrics.
query_metricsEach day's figures as the Metrics Nest app shows them, or weekly or monthly buckets. One row per metric and day (one per reading for metrics read reading by reading), already combined: food and water include what was logged in the app and what other apps wrote to Health, so neve…
query_intradayHour-by-hour readings such as heart rate, kept 90 days. One row per metric, hour and device. Needs the intraday category.
list_nightsOne row per night, keyed by the morning it ended on: bed and wake times, and seconds asleep and in each stage. With several devices, the longest sleep is the night. get_night has the stages.
get_nightOne night in full, including the stage-by-stage hypnogram.
list_workoutsWorkouts with activity, start and end, duration, distance, energy, the heart rate summary and the note. Sets and the route are on get_workout.
get_workoutOne workout in full: the heart rate trace (average bpm and how many readings, minute by minute from the start) and zones, and the exercises and sets and the route when they were shared.
query_logsWhat the person logged in the app: food with calories, macros and fruit and veg portions, drinks by kind (coffee, water, alcohol...), and typed weight. Each entry carries its time and part of day: morning, midday, evening or late. For a day's totals, use query_metrics.
list_exercisesEvery exercise logged in a workout (bench press, squat...), most recently done first, with how many workouts it was in, the first and last day, the heaviest weight lifted in kg (best_weight_kg), and the muscles it trains (null where the person never said, for an exercise of thei…
exercise_historyHow one exercise has gone over time, as the app's exercise screen shows it: every workout it was in, newest first, with the sets (weight kg, reps, RPE, time s, distance m, and reps_left — how many more reps the set had in it, which is how the app asks effort), the best set (the…
muscle_setsWhich muscles the training landed on over a window (default the last 7 days): hard sets per muscle — sets within three reps of failure, or unrated — read against the 10–20 per week most hypertrophy guidance uses, which muscles are still recovering (two or more hard sets in the l…
list_clientsFor a coach: the people who approved you as their coach, with what each lets you read and from when. Pass a client id as `client` to any other tool to read that person. A client who stopped sharing shows as ended.
list_goalsThe goals set in the app: daily or weekly targets on a metric (a calorie ceiling, a water or step target) and journeys toward a value (a weight to reach), each with its progress as the phone last computed it. Needs the goals category.
goal_historyOne goal's progress day by day, newest first: the figure, the fraction of the way there and whether it was met, as the phone computed it on each sync. Use it for how a goal has gone, not only where it stands. The id is from list_goals.
list_badgesThe badges earned in the app, with tier and the time each was earned. Needs the goals category.
propose_workoutSuggest a workout for the person to approve in the Metrics Nest app. This only leaves a suggestion: nothing is planned until they approve it on their phone, where they can also edit or reject it, and no workout is ever created, changed or deleted here. Call list_exercises first…
list_exercise_catalogEvery exercise the Metrics Nest app offers, with the exercise_id propose_workout takes for it, its name and other names, its group, and the muscles it trains. The same for everybody; list_exercises is what this person has actually done.
list_saved_workoutsThe workouts the person saved in the Metrics Nest app to start whenever they like ("Leg day", "Push A"), each with its id, exercises, sets and reps. propose_removing_saved_workout takes the id; propose_saved_workout adds a new one.
propose_saved_workoutSuggest a named workout for the person to keep and start whenever they like ("Leg day"), rather than a session on one day (that is propose_workout). Nothing is saved until they approve it in the Metrics Nest app, where they can edit it first. Same exercises as propose_workout: e…
propose_removing_saved_workoutSuggest taking one of the person's saved workouts away. Nothing is removed until they approve it in the Metrics Nest app; the workouts already done from it stay. The id is from list_saved_workouts.
list_proposalsThe workouts suggested through this connection, newest first, and what became of each: pending, approved, rejected, or expired (unanswered for a week, or past its day). action says which kind each was: plan (a session on a day), save (a named workout to keep) or remove (a saved…
withdraw_proposalTake back a workout this connection suggested that the person has not answered yet: it leaves their list in the app. One they approved, rejected or that expired stays as it is. The id is from propose_workout or list_proposals.
propose_mealSuggest a meal for the person to approve in the Metrics Nest app. This only leaves a suggestion: nothing is logged until they approve it and then log it from their phone, where they can change it on the plate first; no log entry is ever created, changed or deleted here. Give eac…
list_meal_proposalsThe meals suggested through this connection, newest first, and what became of each: pending, approved, rejected, or expired (unanswered for a week, or past its day). log_ids are the food entries it was eaten as — query_logs has them, with meal_id set to the suggestion's id, and…
withdraw_meal_proposalTake back a meal this connection suggested that the person has not answered yet: it leaves their list in the app. One they approved, rejected or that expired stays as it is. The id is from propose_meal or list_meal_proposals.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Optional. 'Bearer mn_live_…', a key from the Metrics Nest iPhone app. Without it, the client signs in with OAuth. |
Details
| Endpoint | https://api.metricsnest.app/mcp (Streamable HTTP) |
| First published | 16 Nov 2026 |
| Last updated | 16 Nov 2026 |
| Registry name | app.metricsnest/metrics-nest |
More data and analytics servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
