What Fitbit data reaches Grok
For Fitbit, Wellness Project uses the Google Health account/API path rather than asking an AI provider to sign into Fitbit. Your Fitbit account is authorized once, supported history is synced into Wellness Project, and the external assistant queries Wellness Project over MCP.
That keeps Google Health and Health Connect separate. Google Health is the Fitbit-successor account/API source. Health Connect is the Android on-device hub used by many apps. You do not need to route a direct Fitbit account connection through Health Connect for this path.
Grok does not receive a bulk wearable export. It asks Wellness Project for the supported rows needed for the question, through the authorized custom MCP connector.
How to connect Fitbit to Grok
Your setup screen may look different.
AI assistants change their settings and navigation frequently. Menu names and steps can vary by web, desktop, or mobile client, device and operating system, plan, account type, version, and staged rollout. Treat the instructions on this page as a current guide and look for the equivalent Apps, Connectors, Plugins, or MCP controls if your version differs.
Connect Fitbit in Wellness Project
Open Settings → Devices → Fitbit and authorize the Google account associated with your Fitbit/Google Health profile. Wellness Project uses Google's Health API underneath.
Confirm Fitbit history has synced
Check recent steps, Active Zone Minutes, sleep stages, resting heart rate, HRV, and workouts. Historical backfill can fill progressively subject to the source API.
Add Wellness Project as a custom connector in Grok
In grok.com, open Settings → Connectors → New Connector → Custom, paste https://wellnessproject.ai/api/mcp, leave Client ID and Client Secret blank, and sign in when Grok opens the Wellness Project authorization flow.
Ask Grok about your real history
Start with a bounded date range and a concrete question. For example: "How did my resting heart rate and sleep stages change over the last month?" The assistant can then request the relevant Wellness Project rows instead of reasoning from a screenshot or one-off export.
What to ask Grok once Fitbit is connected
The useful prompts compare your own history over time. These examples are shaped around the data this source actually sends to Wellness Project.
- How did my resting heart rate and sleep stages change over the last month?
- Which weeks had the most Active Zone Minutes, and did sleep duration hold up?
- Compare my HRV trend with my workout frequency over the last six weeks.
Limits of the Fitbit → Wellness Project → Grok path
Google Health API is the transport for the Fitbit account connection; it is not the same thing as Android Health Connect.
Historical coverage and refresh timing depend on Google's source API. Treat the integration as synced account history, not a live sensor stream.
Grok is reading an authorized Wellness Project MCP connection, not a native Fitbit integration supplied by Grok's developer.
Connect Fitbit, then ask Grok.
Sync the supported history into Wellness Project, authorize Grok, and ask questions against your real trend instead of exporting files or pasting screenshots.
