Metrics Nest

app.metricsnest由 metricsnest.app 發布官方發布者v1.0.1更新於 Nov 16, 2026

Ask Claude, ChatGPT or Cursor about your Apple Health data: workouts, sleep, food. Read-only.

已驗證Streamable HTTP可網頁執行資料與分析

概覽

Metrics Nest 的託管 MCP 服務(api.metricsnest.app),由 metricsnest.app 發布;可選 API 金鑰;Streamable HTTP;26 個工具。

暫無 AI 概覽:以下資訊來自註冊中心條目和服務本身。

發布者
metricsnest.app
端點
api.metricsnest.app
最近檢查

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Metrics Nest,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/app.metricsnest%2Fmetrics-nest/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "metrics-nest": {
      "type": "http",
      "url": "https://api.metricsnest.app/mcp"
    }
  }
}

工具

26

get_profile

Profile

The 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, every call fails until the person renews the share in the app). Call this first.

輸入參數client

list_metrics

List metrics

Every 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.

輸入參數client

query_metrics

Query metrics

Each 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 never add rows together. Paged: follow next_cursor while it is set; meta.truncated names the days a page covers when there are more. A window outside what the share allows is narrowed to it (meta.history_floor and history_ceiling).

輸入參數tofromlimitclientcursormetricgranularity

query_intraday

Query hourly readings

Hour-by-hour readings such as heart rate, kept 90 days. One row per metric, hour and device. Needs the intraday category.

輸入參數datelimitclientcursordevicemetric

list_nights

List nights

One 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.

輸入參數tofromlimitclientcursor

get_night

Get a night

One night in full, including the stage-by-stage hypnogram.

輸入參數clientwake_date必填

list_workouts

List workouts

Workouts with activity, start and end, duration, distance, energy, the heart rate summary and the note. Sets and the route are on get_workout.

輸入參數tofromlimitclientcursoractivity

get_workout

Get a workout

One 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.

輸入參數id必填client

query_logs

Query food, drink and weight logs

What 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.

輸入參數tofromkindlimitclientcursorpart_of_day

list_exercises

List exercises

Every 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 their own). Use an id or name from here in exercise_history. Needs the sets category.

輸入參數client

exercise_history

Exercise history

How 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 heaviest, then most reps) and its weight in kg (top_weight_kg), volume, mean RPE, hard sets (within three reps of failure) and whether it was a PR (heavier, or the same weight for more reps). Nothing is estimated. For "how is my bench press improving", read top_weight_kg and best_set over time. Needs the sets category.

輸入參數tofromclientexercise必填

muscle_sets

Hard sets per muscle

Which 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 last 48 hours), and exercises whose sets were not counted because the person never said what they train. For "what have I been training" or "what should I train next". Needs the sets category.

輸入參數tofromclient

list_clients

List clients

For 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_goals

List goals

The 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.

輸入參數client

goal_history

Goal history

One 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.

輸入參數id必填tofromclient

list_badges

List badges

The badges earned in the app, with tier and the time each was earned. Needs the goals category.

輸入參數client

propose_workout

Suggest a workout

Suggest 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 and give each exercise its exercise_id from there whenever it is one they have done; for one they have not, take its exercise_id from list_exercise_catalog when the app has it, and otherwise leave exercise_id out and give the name. Weights are kg. Make up a new idempotency_key for each suggestion and send the same one only when retrying this exact call: a retry answers the suggestion already made instead of making a second. Works only where the person allowed this connection to suggest workouts (get_profile says can_propose). list_proposals shows what became of each suggestion.

輸入參數title必填clientactivityexercises必填rationaleplanned_for必填idempotency_key必填

list_exercise_catalog

List the exercise catalog

Every 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_workouts

List saved workouts

The 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.

輸入參數client

propose_saved_workout

Suggest a saved workout

Suggest 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: exercise_id from list_exercises or list_exercise_catalog where there is one. Make up a new idempotency_key for each suggestion. Works only where the person allowed this connection to suggest (get_profile says can_propose).

輸入參數title必填clientactivityexercises必填rationaleidempotency_key必填

propose_removing_saved_workout

Suggest removing a saved workout

Suggest 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.

輸入參數clientrationaleidempotency_key必填saved_workout_id必填

list_proposals

List suggested workouts

The 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 one taken away). For an approved one, approved_exercises is what the person approved and edited says whether they changed it; workout_ids are the workouts it was run as, and get_workout has what was actually done.

輸入參數limitclientstatus

withdraw_proposal

Withdraw a suggested workout

Take 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.

輸入參數id必填client

propose_meal

Suggest a meal

Suggest 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 each food a name and, where you can, its grams and its calories and macros for that portion; leave out any figure you do not know rather than guessing. Make up a new idempotency_key for each suggestion and send the same one only when retrying this exact call. Works only where the person allowed this connection to suggest (get_profile says can_propose). list_meal_proposals shows what became of each suggestion.

輸入參數slotitems必填title必填clientrationaleplanned_for必填idempotency_key必填

list_meal_proposals

List suggested meals

The 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 they say what was actually eaten, which may differ from what was suggested.

輸入參數limitclientstatus

withdraw_meal_proposal

Withdraw a suggested meal

Take 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.

輸入參數id必填client

版本歷史

1
  1. v1.0.1最新Nov 16, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。