fitbit-mcp-unofficial
Fitbit MCP server for AI agents
The Fitbit MCP server uses the official Fitbit Web API so agents can work with sleep, heart, movement, body and nutrition context through user-authorized OAuth.
Best for broad wellness agents that need a Fitbit MCP connector combining activity, sleep, HRV, breathing, weight and food/water logs.
MCP server answers
The Fitbit MCP server for AI agents is a local connector provided by fitbit-mcp-unofficial. It uses the official Fitbit Web API and user-authorized OAuth to expose activity, sleep, heart, HRV, body and nutrition context to Claude, Cursor and other MCP-compatible clients. For a new integration, use the Google Health MCP path because Google describes Google Health API as the next generation of Fitbit Web API and schedules the legacy API to stop syncing Fitbit data in September 2026; Fitbit Air workflows follow that same Google Health path. OAuth tokens stay local and Delx does not host a copy of the data.
Compare this connector with the other wellness pathsChoose legacy Fitbit MCP or the Google Health migration pathWhat is the Fitbit MCP server?
The Fitbit MCP server for AI agents is a local connector provided by fitbit-mcp-unofficial. It uses the official Fitbit Web API and user-authorized OAuth to expose activity, sleep, heart, HRV, body and nutrition context to Claude, Cursor and other MCP-compatible clients. For a new integration, use the Google Health MCP path because Google describes Google Health API as the next generation of Fitbit Web API and schedules the legacy API to stop syncing Fitbit data in September 2026; Fitbit Air workflows follow that same Google Health path. OAuth tokens stay local and Delx does not host a copy of the data.
How do I install Fitbit MCP?
Run npx -y fitbit-mcp-unofficial setup, then npx -y fitbit-mcp-unofficial doctor. The Quick Start section below contains the client configuration and provider-specific setup.
What can an agent read from Fitbit?
The available records start with Daily activity, Activity logs, Sleep and sleep stages, Resting heart rate and daily zones. Check Data Availability for scope, device and export limitations before using any result.
Quick Start
npx -y fitbit-mcp-unofficial setup
npx -y fitbit-mcp-unofficial doctor{
"mcpServers": {
"fitbit": {
"command": "npx",
"args": ["-y", "fitbit-mcp-unofficial"]
}
}
}- 01
Create a Fitbit app.
- 02
Use redirect URI http://127.0.0.1:3000/callback.
- 03
Run setup, auth and doctor.
Recommended scopes
activity heartrate profile settings sleep weight nutrition
Data Availability
Daily activity
Steps, calories, distance and zones.
Activity logs
Logged workouts.
Sleep and sleep stages
When Fitbit returns stage data.
Resting heart rate and daily zones
Available on scored days.
Intraday heart-rate samples
Only when app/API access permits intraday data.
HRV, SpO2 and breathing rate
Depends on supported device/account.
Food, water, weight and body composition
When logged.
Continuous device telemetry
Not exposed by Fitbit's public API.
Agent Tools
Profile and onboarding
- fitbit_profile_get
- fitbit_profile_update
- fitbit_onboarding
Start here
- fitbit_connection_status
- fitbit_daily_summary
- fitbit_weekly_summary
Auth and diagnostics
- fitbit_capabilities
- fitbit_agent_manifest
- fitbit_privacy_audit
- fitbit_cache_status
- fitbit_get_auth_url
- fitbit_exchange_code
- fitbit_revoke_access
Profile and devices
- fitbit_get_profile
- fitbit_list_devices
Activity and sleep
- fitbit_get_activity_day
- fitbit_list_activities
- fitbit_get_activity
- fitbit_get_sleep_day
- fitbit_list_sleep
Heart, body and nutrition
- fitbit_get_heart_day
- fitbit_get_heart_intraday
- fitbit_get_hrv_day
- fitbit_get_spo2_day
- fitbit_get_breathing_rate_day
- fitbit_get_weight_day
- fitbit_get_food_day
- fitbit_get_water_day
Prompts and Resources
Prompts
- fitbit_daily_checkin
- fitbit_weekly_review
- fitbit_intraday_investigation
Resources
- fitbit://capabilities
- fitbit://agent-manifest
- fitbit://summary/daily
- fitbit://summary/weekly