Fitbitmcp

What fitbitmcp does

fitbitmcp exposes user-authorized Fitbit data through the Model Context Protocol. Its coverage includes daily activity, logged workouts, sleep and sleep stages, resting heart rate, heart-rate zones, HRV, overnight SpO2, breathing rate, weight, body composition, food and water logs, when those records are available from Fitbit.

The main summary tools turn Fitbit records into agent-ready context. fitbit_daily_summary combines readiness, activity, sleep and heart information for the current day. fitbit_weekly_summary produces a scorecard, compares the previous week and suggests a plan for the following week. Additional prompts support daily check-ins, weekly reviews and investigations of intraday heart-rate samples.

How it works

The package uses Fitbit's official Web API and performs OAuth locally. Access and refresh tokens are kept in ~/.fitbit-mcp/tokens.json with restrictive 0600 permissions, are not printed, and are not returned by MCP tools. The server normalizes API responses before exposing them to an agent.

stdio is the default transport. An optional Streamable HTTP mode runs on loopback, without session IDs, with a health endpoint at /health and MCP requests at /mcp. The default host and port can be adjusted with FITBIT_MCP_HOST and FITBIT_MCP_PORT.

Privacy mode defaults to structured. This removes GPS and secret-bearing fields while retaining complete upstream physiological records and response metadata. Raw Fitbit JSON can be enabled globally with FITBIT_PRIVACY_MODE=raw or selected for an individual call.

Setup and configuration

Create a Fitbit app and set its redirect URI to http://127.0.0.1:3000/callback. The interactive setup flow accepts the Fitbit client ID and secret:

npx -y fitbit-mcp-unofficial setup
npx -y fitbit-mcp-unofficial auth
npx -y fitbit-mcp-unofficial doctor

Recommended OAuth scopes include activity, heartrate, profile, settings, sleep, weight and nutrition. After authorization, configure an MCP client to launch:

{
  "mcpServers": {
    "fitbit": {
      "command": "npx",
      "args": ["-y", "fitbit-mcp-unofficial"]
    }
  }
}

Claude Desktop users can run setup --client claude to write the client configuration. For HTTP mode, start the package with --http; FITBIT_MCP_TRANSPORT=http also selects that transport.

Tools and capabilities

Connection and discovery tools help an agent check readiness before making Fitbit requests. fitbit_connection_status verifies the local setup, while fitbit_data_inventory reports supported domains, scopes, privacy modes and recommended first calls without contacting Fitbit. Capability, manifest, privacy-audit and cache-status tools provide further diagnostics.

Domain-specific tools include:

• Profile and device inspection with fitbit_get_profile and fitbit_list_devices.
• Activity retrieval with fitbit_get_activity_day, fitbit_list_activities and fitbit_get_activity.
• Sleep retrieval with fitbit_get_sleep_day and fitbit_list_sleep.
• Heart, HRV, SpO2 and breathing-rate access through the corresponding daily, series and intraday tools.
• Weight, food and water retrieval by date.
• OAuth URL generation, code exchange and access revocation.

Intraday heart-rate data depends on Fitbit app and API access. Continuous device telemetry is outside the public API coverage. The project is unofficial and is not affiliated with Fitbit or Google; Fitbit's migration toward the Google Health API may affect OAuth, scopes, endpoints or reconnection behavior.