Can Claude Read Fitbit Data? Check the Route and the API Deadline

Claude can discuss Fitbit records that reach a permitted phone health store, or files you choose to upload. Its native mobile Health feature reads Apple Health on iPhone and Health Connect on Android; this is an indirect Fitbit route. The feature is currently a US Pro or Max beta, with Android 14 or later required on Android. We checked these limits on September 30, 2026. Claude iOS guide, Claude Android guide.

Existing Fitbit API connectors need an urgent check. Google says support for the legacy Fitbit Web API ends September 30, 2026, and the API turns off October 30, 2026. Its replacement, the Google Health API, is currently not onboarding new projects. A tutorial for creating a new legacy Fitbit MCP server is therefore a poor starting point. Google's API transition notice.

We make coach steve, an AI running coach you can text. We recommend it if your priority is support for a running goal through a changing week. This guide explains Fitbit data access for Claude; it does not establish a coach steve Fitbit integration or report a hands-on connection test.

Which route fits your question?

Use the phone route for a recent sleep or workout question when its records are present. Use an archive for a dated historical comparison you want to inspect first. If you already pay for a service advertising a Fitbit connection, ask which API it uses and what its migration plan is before relying on continued synchronization.

How does Fitbit data reach Claude on Android?

Google's current documentation calls the companion app Google Health. Its Health Connect connection requires an adult Google Account and Android 9 or later, although Claude's own Health connection needs Android 14 or later. Start in Google Health → Connections → Partner apps → Sync your favorite health apps → Set up. Review the categories and the separate choices for historical or background access. Google Health's Health Connect guide.

Then use Claude's Android Health feature and grant only the reading categories needed for your question. Claude describes this connection as read-only: it cannot write or modify Health Connect records. A provider being connected does not prove that a particular workout, overnight measure or historical period is available to Claude. Claude Android Health documentation.

Keep the direction clear. Google Health importing a record from another app is different from exporting a Fitbit-measured value. Look at the source in the health store, especially if you also wear a second watch or manually log exercise. Google's Health Connect guide distinguishes data recorded by Google Health from data imported through Health Connect. Google's sharing and source guidance.

Is there an official iPhone route?

Yes. Google now documents Apple Health sharing through the Google Health app. It requires iOS 16.4 or later, internet access and an adult Google Account. In Google Health, open Connections → Apps and services → Apple Health, then follow the consent and category choices. Older articles saying Fitbit has no official Apple Health bridge need updating. Google's Apple Health guide.

Google lists exercise, routes, sleep, heart rate and resting heart rate among the categories it can write to Apple Health. HRV appears on the read side, but not the write side. The list does not establish transfer of a Fitbit readiness score. Once relevant records arrive, Claude's iPhone Health connection can read the permitted categories; asking for HRV or readiness does not make a missing field available. Google's directional field list, Claude iPhone permissions.

If the documented app name or menu is absent in your installation, check your account and current app help first. This article verifies the published route, not its activation on every reader's phone.

A worked example: one treadmill run, two records

Imagine a fictional week with three planned runs. Tuesday has a 32-minute treadmill session recorded by a Fitbit device and a second 32-minute entry made manually in another app. These are descriptions of one run, not evidence of two sessions. Saturday's run did not happen because a childcare arrangement fell through.

Before asking Claude to summarize the week, select one record for Tuesday and preserve a note explaining the duplicate. Keep recorded duration, distance estimate, device source and manual entry separate. A useful request is:

The session count is two completed runs, not three. That is a bookkeeping result, not a judgment about effort or fitness. The useful next question concerns available time. A model that recommends reducing training because it sees a missing Saturday entry has skipped the reason the session was missed.

Google's new API distinguishes a reconciled stream from first-party device and manual-entry data. That is another reason to ask a connector operator which stream it supplies, rather than assume every row is an independent Fitbit measurement. We have not verified how a particular Claude connector handles those streams. Google's API data-source description.

Can you use a Fitbit export instead?

For a Google Account, Google's export guide directs users to Google Takeout and says to select Google Health. Download an archive, inspect it locally, and choose a narrow period and relevant fields. Claude supports CSV and JSON uploads; do not upload an entire health archive merely to answer a three-run question. Google's export guide, Claude's supported file types.

For a GPS exercise, Google also documents Google Health → Fitness → activity → More → Export, producing TCX. TCX is not among Claude's listed upload formats. A readable table prepared from the file is a separate conversion step; retain the original and label units, time zone and any transformations. A file upload stays a snapshot rather than a continuing device connection. Google's workout export instructions, Claude upload formats.

What must an existing MCP connector prove?

Claude supports custom remote MCP connectors, but that capability does not establish an official Fitbit connector or a working Google Health API integration. Verify the operator, endpoint, permissions and the API generation it uses. A service still calling the legacy API needs a dated migration plan, not simply an OAuth button. Claude custom connector documentation.

Google says old Fitbit tokens cannot transfer to the new API: users must consent again. Its migration guide forbids keeping both API connections active for the same user after successful migration. Google login alone also does not prove an active Google Health profile; an unlinked account can return an account-not-linked error. A connector should verify the profile and granted permissions before claiming synchronization works. Google's migration requirements.

For a reader, the practical checks are whether the new consent completed, which fields remain available and whether the latest dated record actually arrived. Empty results after an authorization failure are not evidence of zero activity. Do not assume a connector is read-only because Claude's Android phone connection is: custom tools and API permissions require their own inspection.

How do you revoke access or send a workout back?

On iPhone, Google says disconnecting in Google Health leaves Apple Health permissions granted until you turn them off separately. Remove the relevant Google Health sharing and Claude reading permissions. On Android, review each app's Health Connect permissions. Google's Apple Health disconnection instructions, Google's Health Connect controls.

For a custom service, remove its Google Account access and the Claude connector separately. Ask the operator about retained copies; revoking account access does not itself delete data already copied. Google Account access management, Google's retained-data explanation.

None of the routes documented here establishes that Claude can deliver a planned interval session to a Fitbit watch. A text recommendation, a saved exercise record and an executable watch workout are different outcomes. Verify an actual supported write workflow before expecting the last one.

With Fitbit and Claude, a working data route is only part of the job. You still choose which records to trust, explain why a session changed and decide how any advice fits the plan you follow. The duplicate treadmill example above shows a task that needs your judgment even before the training conversation starts.

Our reason to recommend coach steve is its dedicated running-coaching format. Bring the goal and the obstacle into an SMS conversation, then work through a proposal and its tradeoffs. That is the experience we are building for runners who do not want to assemble their own coaching process around a general assistant. This guide does not verify Fitbit ingestion; keep Claude if your priority is investigating those records and its documented route meets your needs. See our AI running coach comparison for the broader choice.

What could a coaching conversation look like?

Suppose you have already checked your Fitbit records, but your week has changed. This fictional exchange shows the coaching approach we are building: understand the problem, discuss a practical option, and leave the choice with you.

CScoach steveAI coach · Simulated conversation

1. You

   I got my Fitbit data into Claude, but I still don’t know how to fit my runs in this week. Work is a mess.

2. coach steve

   What changed? Is it finding time to run, or are you feeling worn out too?

3. You

   Mostly time. I have 30 minutes Thursday and more time Sunday. I still want to work toward my 10K.

4. coach steve

   Let’s look at those days alongside your current plan. What sessions were planned, and what have you already done this week?

5. You

   I can send you that. Please don’t change anything yet.

6. coach steve

   Of course. We’ll talk through an option and why it fits. You can decide whether you want to make the change.

That is why we recommend coach steve for runners who want ongoing coaching by text: the service is designed around the running decision and the conversation that follows. If you enjoy configuring your own assistant, Claude can still be useful. Connecting the records and deciding how to use them are separate jobs.