What this actually does
Out of the box, Claude cannot see your Fitbit data. It has no access to your Fitbit account, and Fitbit publishes no MCP server of its own for Claude to plug into. If you paste a screenshot of last night's sleep, Claude reads that one image, but it has no memory of your history and no way to pull a trend.
Wellness Project is the bridge. Fitbit connects to it over OAuth with a webhook that pushes new data as it lands, so your steps, Active Zone Minutes, sleep stages, and resting heart rate stay current with no manual export. Wellness Project then exposes that synced history to Claude over a single MCP server with read-only access.
The result is a normal Claude chat that can answer questions about your actual Fitbit numbers. This guide is the setup walkthrough; the Fitbit MCP connector page covers the connector itself and the tools it exposes.
How to connect it
Three pieces have to line up: Fitbit has to reach Wellness Project, the MCP server has to be added to Claude, and then you ask. Each step takes about a minute.
Understand what MCP is doing
MCP is the standard that lets Claude read from an outside data source. You are not pasting data into the chat or training a model on it. You are pointing Claude at a server that already holds your synced Fitbit history and letting it read the rows it needs, when it needs them. Nothing is copied in bulk.
Sync Fitbit into Wellness Project
Create a Wellness Project account, then open Settings, Integrations, Fitbit, and authorize over OAuth. A webhook pushes new data as it lands, so steps, Active Zone Minutes, sleep stages, and resting heart rate sync live. This builds the history the MCP server will expose. Free during early access.
Add the MCP server to Claude
In your account settings, generate an API key and copy the Wellness Project MCP server URL. In Claude Desktop or claude.ai, add a connector with that URL and key. Both surfaces support remote MCP servers, so you add it once and it appears in every conversation on that surface.
Ask Claude about your data
Open a chat and ask. "How did my resting heart rate trend this month?" "Did my sleep stages get worse on high Active Zone Minutes days?" "What was my average step count last week?" Claude pulls the structured rows from the server and answers from your Fitbit history rather than a single screenshot.
What to ask once it is connected
The connection is only worth it if the questions get better, and they do. Because Claude reads interpreted history rather than today's isolated figure, the useful prompts are the ones that span time: patterns, baselines, and cause-and-effect across signals.
Ask how your resting heart rate moved across a training block. Ask whether your deep sleep tracks with your hardest Active Zone Minutes days. Ask Claude to flag the week your steps climbed while your sleep fell. Because the same server reads every device you connect, those answers can pull from Fitbit, Apple Health, and Oura together, so the picture is whole instead of split across apps that never compare notes.
Give Claude your real Fitbit history.
Sync Fitbit to Wellness Project over OAuth, add the MCP server to Claude, and ask about your actual trends. Free during early access.