Fitbit MCP
Local-first MCP server that lets AI agents securely access and summarize a user's Fitbit data, manage OAuth locally, inspect privacy/cache/auth state, and use shared wellness profile/onboarding flows.
Retrieve Fitbit activity, sleep/stages, heart rate/zones, HRV, SpO2, breathing rate, weight/body, food, and water data by day or via list endpoints.
Get Fitbit profile and connected devices.
Generate daily/weekly health summaries, normalized wellness context, and bounded heart-rate time series for agent analysis.
Run local setup/auth workflows: get OAuth URL, exchange code, revoke access, and check connection status.
Inspect capabilities, data inventory, agent manifest, demo payloads, cache status, privacy audit, and quickstart guidance.
Read/update the shared Delx Wellness profile and run multilingual onboarding without exposing tokens or secrets.
Use privacy modes (summary/structured/raw) and explicit-intent gates for sensitive actions.
Provides tools for accessing Fitbit activity, sleep, heart rate, HRV, SpO2, weight, and other health data from a Fitbit account.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Fitbit MCP how did I sleep last night?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
⚡ One-command install with Delx Wellness for Hermes:
npx -y delx-wellness-hermes setup— preconfigures this connector and the other 8 in a dedicated Hermes profile.Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop — see the install section below.
HTTP (v2 stateless)
Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:
npx -y fitbit-mcp-unofficial --http
# GET http://127.0.0.1:3000/health
# POST http://127.0.0.1:3000/mcp (sessionless)Env: FITBIT_MCP_HOST, FITBIT_MCP_PORT, FITBIT_MCP_TRANSPORT=http.
Local-first MCP server that connects AI agents to your Fitbit activity, sleep, heart-rate, HRV, SpO2 and weight data.
Unofficial project. Not affiliated with, endorsed by or supported by Fitbit or Google. Use this only with your own Fitbit account and in line with the Fitbit Web API terms.
Platform migration risk: Fitbit is migrating to the Google Health API. OAuth, base URL, scopes and reconnection flows may change in 2026. Treat any breakage as platform drift and check the Fitbit Web API docs before reporting it as a bug.
Built by David Mosiah for people who use Claude, Cursor, Hermes, OpenClaw or other MCP-compatible agents to think about activity, sleep and heart context — without copy-pasting numbers from the Fitbit app.
Part of Delx Wellness, a registry of local-first wellness MCP connectors.
If this connector helps your agent workflow, please star the repo. Stars make the project easier for other AI builders to discover and help Delx keep shipping local-first wellness infrastructure.
Related MCP server: Withings MCP
Why this exists
Fitbit (now under Google) has years of wearable data — daily activity, sleep stages, intraday heart-rate, HRV, SpO2, breathing rate, weight, food and water logs. But its API uses OAuth 2.0 with per-scope authorization and intraday access that varies by app, and the platform is mid-migration to the Google Health API.
This package handles the OAuth dance locally, normalizes responses, and exposes Fitbit through the Model Context Protocol. Tokens never leave your machine. Privacy-mode defaults keep raw payloads opt-in.
Setup in 60 seconds
You'll need a Fitbit app (create one here) with redirect URI http://127.0.0.1:3000/callback.
npx -y fitbit-mcp-unofficial setup # interactive: paste client id + secret
npx -y fitbit-mcp-unofficial auth # opens browser, captures the OAuth code
npx -y fitbit-mcp-unofficial doctor # verifies you're readyRecommended scopes:
activity heartrate profile settings sleep weight nutritionThen add this to your MCP client config:
{
"mcpServers": {
"fitbit": {
"command": "npx",
"args": ["-y", "fitbit-mcp-unofficial"]
}
}
}For Claude Desktop, run setup --client claude and the snippet is written for you.
Try it with your agent
Three things to ask first:
Use fitbit_connection_status to check setup, then run fitbit_daily_summary.
Give me a 5-line operating brief for today.Call fitbit_weekly_summary with response_format=json. Identify my biggest
sleep/activity bottleneck and give me a next-week plan.Use the fitbit_intraday_investigation prompt for date=today, detail_level=1min.
Don't claim anything Fitbit can't actually prove.Data availability
This package uses the official Fitbit Web API. When this README says raw, it means the upstream Fitbit JSON for a supported endpoint — not raw device sensor streams.
Data | Available | Notes |
Daily activity (steps, calories, distance, zones) | ✓ | Standard activity summaries |
Activity logs | ✓ | Logged workouts |
Sleep + sleep stages | ✓ | When Fitbit returns stage data |
Resting heart rate + daily heart-rate zones | ✓ | All scored days |
Intraday heart-rate samples | conditional | Only when the Fitbit app/API access permits intraday |
HRV (overnight) | ✓ | When supported by device/account |
SpO2 (overnight) | ✓ | When supported by device/account |
Breathing rate | ✓ | When supported by device/account |
Weight + body composition | ✓ | When logged |
Food + water logs | ✓ | When logged |
Continuous device telemetry | — | Not exposed by Fitbit's public API |
Tools
Start with these:
fitbit_connection_status— verify local setup before calling Fitbitfitbit_data_inventory— inventory supported data domains, scopes, privacy modes and recommended first calls without calling Fitbit APIs.fitbit_daily_summary— readiness, activity, sleep and heart context for todayfitbit_weekly_summary— scorecard, comparison vs prior week, next-week plan
Auth & diagnostics
fitbit_capabilities,fitbit_agent_manifest,fitbit_privacy_audit,fitbit_cache_statusfitbit_get_auth_url,fitbit_exchange_code,fitbit_revoke_access
Profile & devices
fitbit_get_profile,fitbit_list_devices
Activity
fitbit_get_activity_day,fitbit_list_activities,fitbit_get_activityList calls accept either
afterorbefore, matching Fitbit's mutually exclusive cursor contract. Offset ISO inputs retain their written calendar date and invalid cursors fail before HTTP.
Sleep
fitbit_get_sleep_day,fitbit_list_sleep
Heart & physiology (each takes a date)
fitbit_get_heart_day,fitbit_heart_series,fitbit_get_heart_intradayfitbit_get_hrv_day,fitbit_get_spo2_day,fitbit_get_breathing_rate_day
Body & nutrition (each takes a date)
fitbit_get_weight_day,fitbit_get_food_day,fitbit_get_water_day
Prompts
fitbit_daily_checkin— practical daily health and activity check-infitbit_weekly_review— review trends across activity, sleep and heart contextfitbit_intraday_investigation— investigate one day's intraday heart-rate samples
Resources
fitbit://capabilities,fitbit://agent-manifestfitbit://summary/daily,fitbit://summary/weekly
Privacy & security
OAuth tokens are stored in
~/.fitbit-mcp/tokens.jsonwith0600permissions and are never returned by tools.The server never prints access or refresh tokens.
FITBIT_PRIVACY_MODEdefaults tostructured. Raw Fitbit JSON is opt-in viarawmode or per-call override.Structured mode preserves complete upstream physiological records and response metadata while removing GPS and secret-bearing fields.
Health data is sensitive — do not paste raw payloads publicly.
This is not medical advice. The server exposes user-authorized data for personal AI workflows, not diagnosis or treatment.
Configuration
setup writes most of these into ~/.fitbit-mcp/config.json (0600). Manual env override is supported:
FITBIT_CLIENT_ID=…
FITBIT_CLIENT_SECRET=…
FITBIT_REDIRECT_URI=http://127.0.0.1:3000/callback
# Optional
FITBIT_SCOPES="activity heartrate profile settings sleep weight nutrition"
FITBIT_PRIVACY_MODE=structured # summary | structured | raw
FITBIT_CACHE=sqlite # retained setting; authenticated payload cache/fallback disabledAuthenticated responses bypass both payload caches and offline fallback. Existing SQLite entries are preserved, not inspected or removed by cache status; errors propagate. Anonymous HTTP caching remains available.
Hermes / remote setup
npx -y fitbit-mcp-unofficial setup --client hermes --no-auth
npx -y fitbit-mcp-unofficial auth # run locally if browser auth is needed
npx -y fitbit-mcp-unofficial doctor --client hermes
hermes mcp test fitbitAfter Hermes config changes, use /reload-mcp or hermes mcp test fitbit. Don't restart the gateway for normal data access.
If browser OAuth has to happen on a different machine than Hermes, run auth locally and copy ~/.fitbit-mcp/tokens.json to the server with chmod 600.
Requirements
Node.js 20+
A Fitbit app at https://dev.fitbit.com/apps with redirect URI
http://127.0.0.1:3000/callbackIntraday heart-rate access requires the Fitbit app to be approved for intraday data (varies per app)
Development
git clone https://github.com/davidmosiah/fitbit-mcp.git
cd fitbit-mcp
npm install
npm test
npm run buildTest with MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.jsLinks
Docs site: https://wellness.delx.ai/connectors/fitbit
Legacy docs: https://fitbitmcp.vercel.app/
Delx Wellness registry: https://github.com/davidmosiah/delx-wellness
Connector quality standard: https://github.com/davidmosiah/delx-wellness/blob/main/docs/connector-quality-standard.md
Fitbit Web API: https://dev.fitbit.com/build/reference/web-api/
See also
The full Delx Wellness connector library:
Provider | Package | Repo |
WHOOP | ||
Oura | ||
Garmin | ||
Strava | ||
Fitbit | ||
Withings | ||
Apple Health | ||
Polar | ||
Nourish (nutrition) |
One-command setup for Hermes — preconfigures every connector above plus wellness skills + onboarding: delx-wellness-hermes.
📧 Contact & Support
📨 support@delx.ai — general questions, integration help, partnerships
🐛 Bug reports / feature requests — GitHub Issues
🐦 Updates — @delx369 on X
🌐 Site — wellness.delx.ai
License
MIT — see LICENSE.
Disclaimer
This software is provided as-is. It is not a medical device, does not provide medical advice, and should not be used for diagnosis or treatment. Fitbit is migrating to the Google Health API; the integration boundary may change. Always consult qualified professionals for medical concerns.
Skill or MCP
Same package, two doors. MCP registers tools on stdio/HTTP. The skill can drive the same tools through the CLI when the client has no MCP:
npx -y fitbit-mcp-unofficial call fitbit_connection_status --json '{}'Copy skill/SKILL.md into your agent skills dir.
Release migration
Before upgrading to 0.7.0, review the compatibility and migration notes.
Available Tools
33 toolsfitbit_agent_manifestFitbit Agent ManifestARead-onlyIdempotent
Machine-readable install, runtime and client guidance for AI agents. Does not call Fitbit or expose secrets.
Inputs: client, response_format. Returns: links, oauth, client, hermes, +9 more
fitbit_cache_statusFitbit Cache StatusARead-onlyIdempotent
Show optional local SQLite cache status. Enable with FITBIT_CACHE=sqlite or FITBIT_CACHE=true.
Inputs: response_format. Returns: path, enabled, entries, http_cache, +1 more
fitbit_capabilitiesFitbit MCP CapabilitiesARead-onlyIdempotent
Explain supported Fitbit data, privacy boundaries, recommended agent workflow and project links.
Inputs: response_format. Returns: links, creator, project, mcp_name, +8 more
fitbit_connection_statusFitbit Connection StatusBRead-onlyIdempotent
Check local Fitbit config, token file, Node version, privacy mode, cache readiness and optional MCP client readiness without calling Fitbit or exposing secrets.
Inputs: client, response_format. Returns: ok, node, cache, oauth, +11 more
fitbit_daily_summaryFitbit Daily Health SummaryARead-onlyIdempotent
Build a practical daily summary from Fitbit activity, sleep, heart-rate, HRV and weight data when available. Read-only and non-medical.
Inputs: days, timezone, response_format. Returns: kind, generated_at
fitbit_data_inventoryFitbit Data InventoryARead-onlyIdempotent
Inventory supported Fitbit data domains, auth scope requirements, privacy boundary and recommended first calls. Does not call Fitbit APIs or expose user data.
Inputs: response_format. Returns: auth, kind, links, notes, +12 more
fitbit_demoFitbit DemoARead-onlyIdempotent
Returns realistic example payloads of fitbit_daily_summary, fitbit_wellness_context, and fitbit_get_heart_day so agents see the contract before calling real Fitbit APIs.
Inputs: response_format.
fitbit_exchange_codeExchange Fitbit OAuth CodeA
Exchange a Fitbit OAuth authorization code for local tokens. Tokens are stored locally with 0600 permissions and are never returned. Requires explicit user action: the user must complete browser OAuth and supply the authorization code (agents must not invent codes).
Inputs: code (required), response_format. Returns: ok, note, scope, expires_at, +1 more
fitbit_get_activityFitbit ActivityARead-onlyIdempotent
Get detailed Fitbit activity log by id. Requires activity scope.
Inputs: id (required), privacy_mode, response_format, explicit_user_intent. Returns: data, endpoint, privacy_mode
fitbit_get_activity_dayFitbit Daily ActivityARead-onlyIdempotent
Get daily activity summary, goals and distances for a date. Requires activity scope.
Inputs: date, privacy_mode, response_format. Returns: data, endpoint, privacy_mode
fitbit_get_auth_urlGet Fitbit OAuth URLARead-onlyIdempotent
Generate a Fitbit OAuth authorization URL. Use this first when no local token exists.
Inputs: state, scopes, response_format. Returns: scopes, auth_url, next_step, redirect_uri
fitbit_get_breathing_rate_dayFitbit Daily Breathing RateARead-onlyIdempotent
Get breathing-rate summary for a date when available. Requires heartrate scope. Not medical advice.
Inputs: date, privacy_mode, response_format. Returns: data, endpoint, privacy_mode
fitbit_get_food_dayFitbit Food LogsARead-onlyIdempotent
Get food logs for a date. Requires nutrition scope.
Inputs: date, privacy_mode, response_format. Returns: data, endpoint, privacy_mode
fitbit_get_heart_dayFitbit Daily Heart RateCRead-onlyIdempotent
Get daily heart-rate zones and resting heart rate. Requires heartrate scope. Not medical advice.
Inputs: date, privacy_mode, response_format. Returns: data, endpoint, privacy_mode
fitbit_get_heart_intradayFitbit Heart Rate IntradayARead-onlyIdempotent
Get raw heart-rate intraday samples for a date. For agent work prefer fitbit_heart_series (agent-safe-series/v1 with hard point caps and exact stats). Personal apps can access their own intraday data; third-party apps may require Fitbit approval. Requires heartrate scope. Not medical advice.
Inputs: date, end_time, start_time, detail_level, +2 more. Returns: data, endpoint, privacy_mode
fitbit_get_hrv_dayFitbit Daily HRVARead-onlyIdempotent
Get HRV summary for a date when available. Requires heartrate scope and supported device/data. Not medical advice.
Inputs: date, privacy_mode, response_format. Returns: data, endpoint, privacy_mode
fitbit_get_profileGet Fitbit ProfileBRead-onlyIdempotent
Get the authenticated Fitbit user profile. Requires profile scope.
Inputs: privacy_mode, response_format, explicit_user_intent. Returns: data, endpoint, privacy_mode
fitbit_get_sleep_dayFitbit Daily SleepARead-onlyIdempotent
Get sleep logs and stages for a date. Requires sleep scope. Not medical advice.
Inputs: date, privacy_mode, response_format. Returns: data, endpoint, privacy_mode
fitbit_get_spo2_dayFitbit Daily SpO2BRead-onlyIdempotent
Get SpO2 summary for a date when available. Requires heartrate scope. Not medical advice.
Inputs: date, privacy_mode, response_format. Returns: data, endpoint, privacy_mode
fitbit_get_water_dayFitbit Water LogsARead-onlyIdempotent
Get water logs for a date. Requires nutrition scope.
Inputs: date, privacy_mode, response_format. Returns: data, endpoint, privacy_mode
fitbit_get_weight_dayFitbit Weight LogsARead-onlyIdempotent
Get weight logs for a date. Requires weight scope. Not medical advice.
Inputs: date, privacy_mode, response_format. Returns: data, endpoint, privacy_mode
fitbit_heart_seriesFitbit Heart SeriesARead-onlyIdempotent
Bounded heart-rate time-series for one civil day (agent-safe-series/v1). Exact stats on full-resolution samples plus a downsampled series capped at 500 points. Prefer fitbit_get_heart_day / daily summary first; use this when you need the shape of HR over the day. Shared contract with garmin_activity_series / strava_activity_series / Kindred workout_series. Not medical advice.
Inputs: date, end_time, max_points, start_time, +4 more. Returns: unit, notes, stats, method, +13 more
fitbit_list_activitiesFitbit Activity LogsARead-onlyIdempotent
List Fitbit activity logs. Supports before/after cursor, pagination and privacy modes. Requires activity scope.
Inputs: page, after, limit, before, +5 more. Returns: count, records, endpoint, has_more, +3 more
fitbit_list_devicesList Fitbit DevicesARead-onlyIdempotent
List devices connected to the authenticated Fitbit account. Requires settings scope.
Inputs: privacy_mode, response_format, explicit_user_intent. Returns: data, endpoint, privacy_mode
fitbit_list_sleepFitbit Sleep LogsARead-onlyIdempotent
List Fitbit sleep logs. Supports before/after cursor, pagination and privacy modes. Requires sleep scope. Not medical advice.
Inputs: page, after, limit, before, +5 more. Returns: count, records, endpoint, has_more, +3 more
fitbit_onboardingWellness Onboarding FlowARead-onlyIdempotent
Read-only. Return the 11-question Delx Wellness onboarding flow (en or pt-BR), the current shared profile, missing critical fields, and a cross-connector hint. Use this when the user starts a fresh wellness session and you need to fill out preferred_name, goals, devices, training context, nutrition, preferences, and safety.
Inputs: locale, response_format.
fitbit_privacy_auditFitbit Privacy AuditARead-onlyIdempotent
Return local privacy, cache, token-path and env-presence posture without revealing secret values.
Inputs: response_format. Returns: notes, project, cache_path, token_path, +13 more
fitbit_profile_getGet Shared Wellness ProfileARead-onlyIdempotent
Read the canonical Delx Wellness profile shared with the other wellness MCP connectors (Nourish, Cycle Coach, CGM, etc.). Read-only. Profile stores only what the user typed during onboarding — never OAuth tokens, API keys, or biomarkers.
Inputs: response_format.
fitbit_profile_updateUpdate Shared Wellness ProfileA
Persist a partial patch to the canonical Delx Wellness profile. Requires explicit_user_intent=true after the user confirms they want to save. Rejects secret-like fields (oauth, token, api_key, password, cookie, refresh, session).
Inputs: patch (required), response_format, explicit_user_intent.
fitbit_quickstartFitbit QuickstartARead-onlyIdempotent
Personalized 3-step setup walkthrough for the human user. Adapts to current state (env vars set? token present? what's next?). Call this first when the user asks 'how do I connect Fitbit?'
Inputs: response_format.
fitbit_revoke_accessRevoke Fitbit OAuth AccessADestructive
Revoke the current Fitbit OAuth grant and delete the local token file. Use only when the user explicitly wants to disconnect Fitbit. Gated by explicit_user_intent: true (requires explicit user intent).
Inputs: response_format, explicit_user_intent. Returns: ok, note, token_path, local_tokens_cleared
fitbit_weekly_summaryFitbit Weekly Health ReviewARead-onlyIdempotent
Build a weekly Fitbit scorecard with activity, sleep, heart-rate, HRV availability, bottlenecks and actions. Read-only and non-medical.
Inputs: days, timezone, compare_days, response_format. Returns: kind, generated_at
fitbit_wellness_contextFitbit Wellness ContextBRead-onlyIdempotent
Normalize Fitbit sleep and activity load into the shared wellness_context shape for recommendation engines.
Inputs: days, notes, soreness, timezone, +2 more. Returns: notes, source, soreness, generated_at, +2 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 33 tools
Several tool clusters blur together: fitbit_data_inventory, fitbit_capabilities, and fitbit_agent_manifest all describe supported data, privacy, and guidance; fitbit_connection_status and fitbit_privacy_audit both inspect local state. The confusing fitbit_get_profile vs fitbit_profile_get pair is especially risky because one returns Fitbit profile data and the other returns the Delx wellness profile.
All tools share the fitbit_ prefix and snake_case, but the naming conventions are mixed: verb_noun forms like fitbit_get_activity_day coexist with noun-only names like fitbit_daily_summary, and reversed noun_verb forms like fitbit_profile_get and fitbit_profile_update. The near-match between fitbit_get_profile and fitbit_profile_get highlights the inconsistency and increases misselection risk.
33 tools is too many for a well-scoped MCP server. A large portion are meta, setup, and status tools—inventory, manifest, capabilities, quickstart, demo, connection status, cache status, and privacy audit—that overlap and could be consolidated without losing functional coverage.
The server covers the Fitbit wellness domain well: OAuth lifecycle, profile, devices, activity, sleep, heart rate, HRV, breathing rate, SpO2, weight, food, water, plus daily/weekly summaries and a shared wellness profile. Minor gaps exist such as lack of sleep-log-by-id detail or explicit token refresh, but core read-only Fitbit workflows have no dead ends.
Maintenance
Related MCP Connectors
MCP server for Withings health data — sleep, activity, heart, and body metrics.
Official Fibery MCP server: query and update your workspace from any AI client via OAuth.
Hosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc.
Multi-tenant hosted MCP server for Oura Ring — 21 read-only tools, OAuth per user.
Related MCP Servers
- AlicenseBqualityBmaintenanceA local-first MCP server that enables AI agents to read user-authorized Google Health API v4 data from Fitbit, Pixel Watch, and partners via OAuth, with tokens never leaving the machine.26875 npm84MIT
- AlicenseBqualityBmaintenanceLocal-first MCP server that connects AI agents to your Withings body, sleep, activity and heart data.23224 npm5MIT
- AlicenseBqualityBmaintenanceLocal-first MCP server that connects AI agents to your Garmin sleep, HRV, Body Battery, stress, training readiness and activities, keeping tokens on your machine.242346 npm13MIT
- AlicenseBqualityBmaintenanceLocal-first MCP server that connects AI agents to your Polar training, sleep, Nightly Recharge and continuous-sample data.38348 npm6MIT