How to Get Google Fitbit Data Into ChatGPT
ChatGPT can read your Apple Health data. WHOOP, Oura and Garmin all reach it that way. Fitbit does not, and OpenAI's own documentation does not list it — so the question has a real answer rather than a documentation gap. It has four answers, and which one is right depends almost entirely on whether you own an iPhone or an Android phone.
We earn nothing from this page. No affiliate links, no sponsorship, no paid placement, and no relationship with any tool named here. We did not install or run any of the software described — see our editorial standards for exactly what that means.
The short answer
If you have an iPhone, this is now solved and it is free. Google Health version 5.05, released 2 August 2026, added two-way Apple Health sync. Turn that on and your Fitbit data flows into Apple Health, which ChatGPT can already read — no third party, no subscription, no maintenance. If you have an Android phone, there is no equivalent, because ChatGPT does not read Android's Health Connect and Fitbit's data lands there. You need a bridge, and the cheapest durable one is a self-hosted Model Context Protocol server reading the Google Health API. Expect to re-authorise it about once a week.
Why Fitbit is not in ChatGPT's list
OpenAI's documentation for Health in ChatGPT lists what you can connect. It is a short list, and the omission is structural rather than a Fitbit-specific rejection.
| Source | How it reaches ChatGPT | Available to you? |
|---|---|---|
| Apple Health | Direct, native | iOS mobile only |
| US provider portals, One Medical, Function Health | Direct, native | US only |
| WHOOP | Via Apple Health | Yes, if it shares to Apple Health |
| Oura | Via Apple Health | Yes, if it shares to Apple Health |
| Garmin | Via Apple Health | Yes, if it shares to Apple Health |
| Fitbit / Google Health | Not listed | Requires a bridge |
Look at the pattern. Every wearable OpenAI does support reaches ChatGPT the same way — by writing into Apple Health. Fitbit is absent for one reason: until August 2026 it could not write to Apple Health at all. The Fitbit app historically synced one way, and on Android it writes to Health Connect instead, which is a different platform entirely and one ChatGPT does not read.
That is why this problem became solvable at a specific moment rather than gradually. It was not OpenAI adding Fitbit support. It was Google removing the gap that made Fitbit support pointless.
Route 1 — iPhone: the native path
This is the answer for most people, and it takes about two minutes.
Read the release notes, not the help page
Google's own support documentation continued to describe write-back to Apple Health as arriving "later in 2026" after the feature had already shipped in August. This is a case where the documentation lagged the release by some time, and it is why several third-party write-ups of this feature are wrong. The app's version history is the reliable source.
Route 2 — export and paste
Works on both platforms, requires no software, and is the option most guides recommend first. It is also worse than it sounds.
You can export a selection of your data, or request a full account archive, from Google Takeout or from Data Export in Fitbit settings. A full archive takes time to generate and arrives by email link. Then you paste it into a conversation.
The problems are structural, not fixable:
- It is frozen the moment you export. Tomorrow's question needs tomorrow's export.
- Large histories blow the context window. A year of minute-level heart rate is not a prompt. You end up pre-processing in a spreadsheet, which means doing the analysis yourself and asking ChatGPT to interpret a summary you produced.
- Provenance disappears. Once data is pasted, the model cannot tell which rows are measurements and which are your notes.
Use it for a one-off question you could not otherwise answer. Do not build a habit on it.
Route 3 — self-hosted MCP bridge
The durable free option, and the only one that keeps your health history on hardware you control.
The mechanism is a Model Context Protocol server. It reads the Google Health API, stores what it needs, and exposes tools that an AI assistant can call during a conversation. ChatGPT registers it as a custom connector; Claude, Grok and Mistral can consume the same server.
| Project | Shape | Notable |
|---|---|---|
| google-health-fitbit-mcp | Local stdio, 29 read-only tools | Most complete local option. Tokens stored on disk with restricted permissions and never returned by any tool. Ships a demo mode with synthetic payloads so an agent can learn the contract before touching real data. |
| google-health-mcp-server | Local, plus Obsidian sync | Includes a connection-status tool for diagnosing which metrics actually return data, and can write daily notes into an Obsidian vault. Returns raw rollup points alongside normalised values so nothing is lost to a field-mapping guess. |
| fitbit-health-mcp | Remote HTTP MCP, ChatGPT Connector | The only one of the three aimed specifically at registering with ChatGPT as a remote connector, separating MCP OAuth from Google OAuth. Single-user reference implementation rather than a platform. |
The weekly chore you are adopting
Every Google Health API scope is a restricted scope. Google requires OAuth verification plus an annual paid security assessment before an app can use them in production, which is not viable for a personal tool. The workaround every one of these projects uses is to keep the consent screen in Testing mode with you as the only test user — and Google issues Testing-mode refresh tokens that expire after seven days.
Two practical consequences. First, expect a re-consent prompt roughly weekly; ten seconds in a browser. Second, do not build anything time-critical on top of an unattended sync. Projects that host on ephemeral free-tier filesystems can lose their token on any restart, and Google's OAuth testing policy can require periodic re-authorisation independently.
If that weekly friction is what stops you, Route 4 exists precisely to absorb it.
Route 4 — a hosted bridge
Services that hold a synced copy of your Fitbit history and serve it to assistants over MCP. You connect Fitbit once over OAuth, add the service as a connector, and the maintenance is someone else's problem.
We are going to describe these carefully rather than recommend one. The vendor we found publishing setup documentation describes a subscription tier, MCP connectors for several assistants, and a claim that only the rows requested during an active conversation are transmitted rather than a bulk copy. Those are the vendor's own claims and we have not independently verified any of them.
Before paying any hosted service for your health data, ask four questions:
- Where is my data stored, and is it encrypted at rest?
- Is my access revocable, and does revoking it actually delete anything?
- Do you sell, share or analyse it? With whom?
- Can I export everything, in a usable format, if I leave?
The trade is straightforward: you are buying the removal of a weekly chore, and paying for it with a standing trust decision about a third party's handling of your health history. That is a reasonable trade for some people and a bad one for others. Neither answer is wrong.
What will not make it across
Whatever route you choose, some things stay behind. Better to know now than to spend an evening wondering why ChatGPT keeps hallucinating a score.
- Readiness, Sleep Score and Cardio Load. These are computed by Fitbit, not stored as measurements, so there is nothing to read. OpenAI's documentation explicitly warns that some proprietary scores may not transfer. This applies to every route including the native one.
- Sleep stage percentages on iPhone. The raw sleep session and its stages may transfer; whether the derived score does is a separate question.
- Anything gated behind Google Health Premium on the Google side. Not a transfer issue, but worth stating: the coach, deeper sleep insights and adaptive plans remain behind the subscription regardless.
- Write access. ChatGPT cannot write back to Apple Health or any connected record. Read-only in every route here.
Which route, in one line each
| Route | Platforms | Cost | Effort | Privacy |
|---|---|---|---|---|
| iOS via Apple Health | iPhone only | Free | Two minutes, one time | Apple, Google and OpenAI under published terms |
| Export and paste | Both | Free | Every single time | Whatever you paste it into |
| Self-hosted MCP | Both | Free plus a server | Setup, then weekly re-consent | Your hardware; only requested rows leave |
| Hosted bridge | Both | Subscription | Connect once | A third party's servers |
Frequently asked
Can ChatGPT read my Fitbit data?
Not directly. OpenAI's documentation for Health in ChatGPT lists Apple Health, supported US provider portals, One Medical and Function Health, and documents WHOOP, Oura and Garmin as reaching ChatGPT via Apple Health. Fitbit appears in neither list. On iPhone you close the gap by syncing Google Health into Apple Health first. On Android there is no equivalent, because ChatGPT does not read Health Connect.
What is the easiest way to get Fitbit data into ChatGPT?
On an iPhone, enable Sync to Apple Health in Google Health, then connect Apple Health from the Health tab in ChatGPT. Free, native, no third party, updates automatically. It requires Google Health 5.05 or later, released 2 August 2026, and ChatGPT's Apple Health connection is iOS-only.
How do I get Fitbit data into ChatGPT on Android?
You need a bridge. Fitbit's data lands in Android's Health Connect, which ChatGPT does not read. The practical route is an MCP server that reads the Google Health API and registers with ChatGPT as a custom connector; several open-source projects do this. Expect to re-authorise about weekly, because Google Health scopes are restricted and Testing-mode refresh tokens expire after seven days.
Will my Fitbit Readiness and Sleep Score transfer?
Probably not. Those are proprietary scores computed by Fitbit rather than stored as raw measurements, and OpenAI's documentation warns that some proprietary scores may not transfer. What transfers is the underlying data: steps, heart rate, active zone minutes, and sleep sessions with stages.
Is it safe to give an AI assistant my health data?
It depends on the route. The native iOS path keeps data between Apple, Google and OpenAI under their published terms. A self-hosted MCP server keeps it on your hardware and sends only the rows the assistant requests during a conversation. A third-party hosted bridge puts your health history on someone else's servers, which is a materially different trust decision. Read what each route actually does with the data before choosing, and revoke access when you stop.
Related
- Google Health Data: Portals, Scores and AI — the cluster index, including the platform split in full
- Google Health Alternatives: 7 Dashboards for Fitbit Data — if what you actually want is to see your history rather than query it
- Recreating WHOOP on Google Fitbit — the data these routes carry, and what it can and cannot produce
- Privacy — what this site itself stores, which is nothing
Sources
- Health in ChatGPT — OpenAI Help Center. The primary source for which sources are supported, which wearables route via Apple Health, and the proprietary-score caveat
- How do I use Apple Health with the Google Health app? — Google Health Help Center
- Google Health adds two-way Apple Health syncing on iPhone — 9to5Mac, 3 August 2026. Confirms version 5.05 and the categories written
- Google Health can now sync to Apple Health — notes that the category list is incomplete and that documentation lagged the release
- How do I use Health Connect with the Google Health app? — Google Health Help Center. Source of the Android write path
- Connect third-party devices and apps to the Google Health app — Google Health Help Center
- How do I export my Fitbit data? — Google Help Center
- Google Health API scopes — Google for Developers. Basis for the restricted-scope and re-authorisation points
- me3e3e/google-health-fitbit-mcp — README
- madfreakz/google-health-mcp-server — README, including its own account of the seven-day token constraint
- Ma1ndo26rc/fitbit-health-mcp — README and stated limitations