The API's ceilings are stated where you will actually read them: 100 days for a sleep range, one year for a heart-rate range, 1,095 days for nutrition and Active Zone Minutes, 30 days for the activity time series. It is a small thing that saves a lot of failed calls. Everything returns the raw JSON response, which is honest about what it is — no reshaping and no derived metrics — and it means an answer you get back is grounded in the fields Fitbit actually publishes. It reads only: nothing here logs a meal or changes a goal.
A read-only Fitbit server returning the raw API responses for weight, sleep, heart rate, activity, nutrition and goals, addressed either by a period ending today or by an explicit date range.
- Weight entries over a period such as 1d, 7d, 30d, 3m, 6m or 1y
- Sleep logs across a start and end date, with the API's 100-day maximum range stated on the tool
- Heart rate two ways: a period ending today or on a given date, and an explicit date range capped at one year
- Exercise and activity logs after a given date, with a limit
- Nutrition: a full food log for one date with daily totals and individual entries carrying calories, protein, carbs, fat, fibre and sodium, plus caloriesIn and water as a period or over a range of up to 1,095 days
- Daily activity summaries with goals, steps, calories, distances and heart rate zones
- Activity goals for daily and weekly periods, covering steps, distance, calories, floors, active minutes and active zone minutes
- Activity time series over a range of up to 30 days for steps, distance, calories, activityCalories and caloriesBMR
- Active Zone Minutes time series over up to 1,095 days, broken into fat burn, cardio and peak
- The user profile
A Fitbit account and a registered Fitbit application, whose client ID and secret go in FITBIT_CLIENT_ID and FITBIT_CLIENT_SECRET.
One command plus a key — npm install -g mcp-fitbit, then supply credentials