Fitbit MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Fitbit MCP by usefulapi is answering right now. Last checked 14 min ago. It exposes 17 tools. Last commit 12 Oct 2026.

Read Fitbit profile, activity, sleep, heart rate and device data.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

99 ms

Response time

average over 24h

Stars

last commit 12 Oct 2026

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 October 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

7 Oct a tool changed version

1 Oct a tool changed version2 times that day

and 4 more, back to 1 October 2026

Nothing serious here today

Today is the operative word: we check Fitbit MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add fitbit --transport http https://fitbit.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "fitbit": {
      "url": "https://fitbit.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.fitbit]
url = "https://fitbit.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "fitbit": {
      "url": "https://fitbit.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "fitbit": {
      "url": "https://fitbit.usefulapi.io/mcp"
    }
  }
}

Available tools 17

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fitbit

fitbit_activity_goals

The user's activity goals (steps/distance/calories/active-minutes) for the daily or weekly period. Fitbit REST: GET /1/user/-/activities/goals/{period}.json.

fitbit_activity_time_series

Activity metric time series over a date range (e.g. daily steps for a week). Max 1095 days. Fitbit REST: GET /1/user/-/activities/{resource}/date/{startDate}/{endDate}.json.

fitbit_body_fat_log

Body fat percentage log entries for a date. Fitbit REST: GET /1/user/-/body/log/fat/date/{date}.json.

fitbit_breathing_rate

Breathing (respiratory) rate summary for a date or range. Fitbit REST: GET /1/user/-/br/date/{date}[/{endDate}].json.

fitbit_cardio_score

Cardio fitness score (VO2 max estimate) for a date or range. Fitbit REST: GET /1/user/-/cardioscore/date/{date}[/{endDate}].json.

fitbit_daily_activity_summary

Daily activity summary for a date — steps, distance, floors, calories, active minutes, and the day's logged activities. Fitbit REST: GET /1/user/-/activities/date/{date}.json.

fitbit_food_log

Food/nutrition log for a date — logged foods and daily nutrition totals (calories, macros). Fitbit REST: GET /1/user/-/foods/log/date/{date}.json.

fitbit_get_devices

List the user's Fitbit devices/trackers (battery, last sync, version). Fitbit REST: GET /1/user/-/devices.json.

fitbit_get_profile

The current user's Fitbit profile (name, age, gender, height, timezone, member since, avatar, etc.). Fitbit REST: GET /1/user/-/profile.json.

fitbit_heart_rate

Heart-rate time series — resting HR and time in each HR zone. Give a single date + period, OR a date + endDate range. Fitbit REST: GET /1/user/-/activities/heart/date/{date}/{period|endDate}.json.

fitbit_hrv

Heart rate variability (HRV) summary for a date or range. Fitbit REST: GET /1/user/-/hrv/date/{date}[/{endDate}].json.

fitbit_lifetime_stats

Lifetime and best-ever activity statistics (total steps, distance, floors; personal bests). Fitbit REST: GET /1/user/-/activities.json.

fitbit_skin_temperature

Skin temperature (relative to baseline) for a date or range. Fitbit REST: GET /1/user/-/temp/skin/date/{date}[/{endDate}].json.

fitbit_sleep_log

Sleep logs for a date (or date range) — stages/levels, duration, efficiency, start/end times. Fitbit REST: GET /1.2/user/-/sleep/date/{date}[/{endDate}].json.

fitbit_spo2

Blood oxygen saturation (SpO2) summary for a date or range. Fitbit REST: GET /1/user/-/spo2/date/{date}[/{endDate}].json.

fitbit_water_log

Water intake log for a date. Fitbit REST: GET /1/user/-/foods/log/water/date/{date}.json.

fitbit_weight_log

Body weight log entries for a date. Fitbit REST: GET /1/user/-/body/log/weight/date/{date}.json.

Endpoints

URL	Transport	State	Latency	Checked
https://fitbit.usefulapi.io/mcp	streamable-http	answering	76 ms	14 min ago

Alternatives to Fitbit MCP by usefulapi

same job, measured the same way

Oura MCP by usefulapi

by usefulapi

Read sleep, readiness, activity, stress, heart rate and workouts from the Oura Ring.

10 tools answering

Vital MCP by usefulapi

by usefulapi

Read wearables and lab health data — sleep, activity, workouts, timeseries, lab tests and orders.

21 tools answering

Fitbitmcp

by davidmosiah

Privacy-first, unofficial Fitbit MCP server for AI health, sleep, activity and heart-rate agents.

176 installs/wk local only

Oura Ring

by osjayaprakash

Read-only Oura Ring sleep, readiness, activity, stress and heart rate data (OAuth2)

140 installs/wk local only

Oura Ring MCP Server

by jordanburke

Oura Ring MCP server for the Oura API v2: sleep, readiness, activity, heart rate, and more.

186 installs/wk local only

Withings Health Data

by akutishevsky

MCP server for Withings health data — sleep, activity, heart, and body metrics.

answering

Oura Ring

by yasuakiomokawa

MCP server for Oura Ring API v2 (sleep, activity, readiness, heart rate, workouts).

96 installs/wk local only

Ouramcp

by davidmosiah

Privacy-first, unofficial Oura MCP server for AI health, sleep, activity and heart-rate agents.

273 installs/wk local only

Fitbit MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Fitbit MCP by usefulapi do?

It exposes 17 tools, read directly from the server on our last check. Among them: fitbit_activity_goals, fitbit_activity_time_series, fitbit_body_fat_log, fitbit_breathing_rate, fitbit_cardio_score, fitbit_daily_activity_summary and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Fitbit MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 99 ms. The bar chart above shows every period we have measured.

How do I connect Fitbit MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Fitbit MCP by usefulapi need an API key?

No. Fitbit MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Fitbit MCP by usefulapi?

It answers our handshake in 99 ms on average, which is faster than 86% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Fitbit MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.