All studies
Research·October 15, 2026·4 min read

Can Claude Log Your Weight or Water From a Chat

Yes, but only after you connect the custom connector and tick the logging scope. Reading is on by default. Logging stays off until you tick it.

Yes, you can ask Claude to log your weight or water, but only after you connect the HealthOS custom connector and tick the logging scope. Until then the write tools are off, so Claude cannot add anything even if it can already read your activity, sleep or glucose data.

Can I ask Claude to log my weight?

Yes. The phrase does not need to be clever. Ask Log my weight: 76 kg or Log 500 ml of water in a chat where the connector is switched on. If the logging scope is not ticked, Claude may summarise data or answer questions, but any write request fails or is refused.

The mistake people make is assuming a fresh connection can do everything. It cannot. When you approve the connector, reading is ticked by default. Logging data for you starts off. That asymmetry is deliberate: reading your own history back to you is lower risk than creating new entries in your record.

Reading is on by default. Logging stays off until you tick it.

What you need to tick to make writes work

Set up happens once.

  1. 1.Open Claude on claude.ai, the desktop app or the mobile app.
  2. 2.Go to Settings → Connectors and choose Add custom connector.
  3. 3.Paste https://mcp.healthosx.com/mcp and press add.
  4. 4.Sign in, then tick Logging data for you before approving.
  5. 5.In a new chat, open the tools menu and switch the connector on.

On the consent screen you will see grouped scopes. Activity, sleep, glucose, meals, blood tests and other reading scopes are ticked by default. Logging data for you is not. That tool switch in step 5 is separate from the connection itself. A connector can be installed but not active in a particular chat.

Custom connectors work on every Claude plan. On Team and Enterprise plans an owner may have to add the connector for the organisation first. If you do not see the option, that is the likely reason.

Reading and logging are separate permissions
ScopeDefaultWhat it permits
Activity, sleep, glucose, meals, blood testsOnClaude can read the latest synced data
Logging data for youOffClaude can create weight or water entries

Scroll the table sideways for the rest →

What the consent screen controls for a custom Claude connector. Deleting requires confirmation in chat.

Why Claude cannot write just because it can read

Claude only gets what you ticked, and only when a question needs it. Claude gets an OAuth token that carries the scopes you approved. A tool call only succeeds when the token holds the right scope. Reading scopes do not grant write access. If you did not tick Logging data for you, the token simply has no write permission.

The grant is also bounded in time and rate. Access tokens last 1 hour, refresh tokens rotate on each use, and the whole connection lasts at most 365 days before you approve again. Each connection is limited to 60 tool calls a minute and 2,000 tool calls a day (UTC) per connection, which is plenty for conversation but stops runaway loops.

1 hour
OAuth access token lifetime
60
tool calls allowed per minute
2,000
tool calls allowed per day
365 days
maximum connection before re-approval

Create tools use an idempotency_key according to the provided pages. The docs only say that create tools take an idempotency_key. They do not say that asking again in chat reuses the same key, so duplicate-free retries are not automatic. If a retry does reuse the same key, the write is created once.

If you approved the connector without Logging data for you, the provided pages do not specify how to add logging after approval. Check Settings → Connected apps in the connected account to review or manage the connector.

What gets logged, and where it appears

A successful logging request uses the connector's create tool to record the value and time you asked. The examples cover weight in kilograms and water in millilitres. If you ask for something outside the logging scope, the request simply has no permission to proceed.

The provided pages do not confirm whether that write is a manual log in the connected account or a direct Apple Health write. Check the live HealthOS connector page before relying on either description. Apple Health and glucose data come from the iPhone app that syncs to the connector, so the assistant sees what your phone last synced. If your phone has not synced recently, the assistant can tell you the last sync time.

The provided pages only say create tools use an idempotency_key. They do not describe whether multiple logs build a time series or whether daily weight shows a trend, so do not infer trend behavior from the available documentation.

That distinction matters. People expect a chat assistant to update the same weight widget on their phone. The documentation does not confirm that the chat writes directly to Apple Health; what it shows is that Apple Health data still depends on the phone sync.

What still needs your attention

This is wellness data, not a medical device. Claude can be wrong, so check anything important with a doctor. Do not rely on a chat assistant for clinical decisions. You can disconnect any time in the connected account under Settings → Connected apps, in the app or on the web, and access stops straight away.

If you want to see it in your own numbers, set it up from the HealthOS connector page. It has the step by step setup for Claude and the short list of what you can ask once logging is ticked.

Written by

HealthOS Research

Keep reading