Read Fitbit profile, activity, sleep, heart rate and device data. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"fitbit": {
"url": "https://fitbit.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"fitbit": {
"type": "http",
"url": "https://fitbit.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Fitbit API key.
Create one in Fitbit → Settings → API. Your token is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Fitbit API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Fitbit connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
fitbit_get_profile | read | 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_get_devices | read | Get devices List the user's Fitbit devices/trackers (battery, last sync, version). Fitbit REST: GET /1/user/-/devices.json. |
fitbit_daily_activity_summary | read | 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_activity_time_series | read | 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_activity_goals | read | 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_lifetime_stats | read | Lifetime stats Lifetime and best-ever activity statistics (total steps, distance, floors; personal bests). Fitbit REST: GET /1/user/-/activities.json. |
fitbit_heart_rate | read | 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_sleep_log | read | 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_weight_log | read | Weight log Body weight log entries for a date. Fitbit REST: GET /1/user/-/body/log/weight/date/{date}.json. |
fitbit_body_fat_log | read | Body fat log Body fat percentage log entries for a date. Fitbit REST: GET /1/user/-/body/log/fat/date/{date}.json. |
fitbit_food_log | read | 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_water_log | read | Water log Water intake log for a date. Fitbit REST: GET /1/user/-/foods/log/water/date/{date}.json. |
fitbit_spo2 | read | SpO2 Blood oxygen saturation (SpO2) summary for a date or range. Fitbit REST: GET /1/user/-/spo2/date/{date}[/{endDate}].json. |
fitbit_hrv | read | HRV Heart rate variability (HRV) summary for a date or range. Fitbit REST: GET /1/user/-/hrv/date/{date}[/{endDate}].json. |
fitbit_breathing_rate | read | Breathing rate Breathing (respiratory) rate summary for a date or range. Fitbit REST: GET /1/user/-/br/date/{date}[/{endDate}].json. |
fitbit_cardio_score | read | Cardio score Cardio fitness score (VO2 max estimate) for a date or range. Fitbit REST: GET /1/user/-/cardioscore/date/{date}[/{endDate}].json. |
fitbit_skin_temperature | read | Skin temperature Skin temperature (relative to baseline) for a date or range. Fitbit REST: GET /1/user/-/temp/skin/date/{date}[/{endDate}].json. |
fitbit_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
fitbit_request_feature | Request a missing feature Tell usefulapi that the user needs something the Fitbit tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
fitbit_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Fitbit tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
fitbit_cancel_subscription | Cancel the Pro subscription Cancel the caller's Fitbit Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run fitbit_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Fitbit server only. Subscribe with fitbit_upgrade (it returns a Stripe Checkout link). Cancel any time with fitbit_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running fitbit_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Fitbit. The server calls the Fitbit API with your own Fitbit access, so it sees only the data that your account can see.
The login page asks for your Fitbit API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Fitbit API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Fitbit API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Fitbit.
All 17 Fitbit tools are marked read-only.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Fitbit server only. Run fitbit_usage_status to see how many calls you used.
Ask the AI to run fitbit_upgrade: it returns a Stripe Checkout link. To cancel, run fitbit_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with fitbit_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.