Fitbit MCP by usefulapi is an MCP server published by io.usefulapi, hosted at fitbit.usefulapi.io. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 17 tools, including fitbit_get_profile, fitbit_get_devices, fitbit_daily_activity_summary, fitbit_activity_time_series, fitbit_activity_goals.
Read Fitbit profile, activity, sleep, heart rate and device data.
4,081 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
The current user's Fitbit profile (name, age, gender, height, timezone, member since, avatar, etc.). Fitbit REST: GET /1/user/-/profile.json.
No parameters.
{
"name": "fitbit_get_profile",
"title": "Get profile",
"description": "The current user's Fitbit profile (name, age, gender, height, timezone, member since, avatar, etc.). Fitbit REST: GET /1/user/-/profile.json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "Get profile",
"readOnlyHint": true
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
List the user's Fitbit devices/trackers (battery, last sync, version). Fitbit REST: GET /1/user/-/devices.json.
No parameters.
{
"name": "fitbit_get_devices",
"title": "Get devices",
"description": "List the user's Fitbit devices/trackers (battery, last sync, version). Fitbit REST: GET /1/user/-/devices.json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "Get devices",
"readOnlyHint": true
}
}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.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
{
"name": "fitbit_daily_activity_summary",
"title": "Daily activity summary",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
}
}
},
"annotations": {
"title": "Daily activity summary",
"readOnlyHint": true
}
}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.
| Parameter | Type | Description |
|---|---|---|
| endDate * | string | Range end date, yyyy-MM-dd or 'today' (required). |
| resource * | string | Activity metric to fetch (required). |
| startDate * | string | Range start date, yyyy-MM-dd or 'today' (required). |
{
"name": "fitbit_activity_time_series",
"title": "Activity time series",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"resource",
"startDate",
"endDate"
],
"properties": {
"endDate": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Range end date, yyyy-MM-dd or 'today' (required)."
},
"resource": {
"enum": [
"steps",
"distance",
"calories",
"floors",
"elevation",
"minutesSedentary",
"minutesLightlyActive",
"minutesFairlyActive",
"minutesVeryActive",
"activityCalories"
],
"type": "string",
"description": "Activity metric to fetch (required)."
},
"startDate": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Range start date, yyyy-MM-dd or 'today' (required)."
}
}
},
"annotations": {
"title": "Activity time series",
"readOnlyHint": true
}
}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.
| Parameter | Type | Description |
|---|---|---|
| period * | string | Goal period — 'daily' or 'weekly' (required). |
{
"name": "fitbit_activity_goals",
"title": "Activity goals",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"period"
],
"properties": {
"period": {
"enum": [
"daily",
"weekly"
],
"type": "string",
"description": "Goal period — 'daily' or 'weekly' (required)."
}
}
},
"annotations": {
"title": "Activity goals",
"readOnlyHint": true
}
}Lifetime and best-ever activity statistics (total steps, distance, floors; personal bests). Fitbit REST: GET /1/user/-/activities.json.
No parameters.
{
"name": "fitbit_lifetime_stats",
"title": "Lifetime stats",
"description": "Lifetime and best-ever activity statistics (total steps, distance, floors; personal bests). Fitbit REST: GET /1/user/-/activities.json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "Lifetime stats",
"readOnlyHint": true
}
}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.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
| period | string | Period ending at `date` — used only when `endDate` is omitted (default '1d'). |
| endDate | string | Range end date, yyyy-MM-dd or 'today' — if given, `period` is ignored. |
{
"name": "fitbit_heart_rate",
"title": "Heart rate",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
},
"period": {
"enum": [
"1d",
"7d",
"30d",
"1w",
"1m"
],
"type": "string",
"default": "1d",
"description": "Period ending at `date` — used only when `endDate` is omitted (default '1d')."
},
"endDate": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Range end date, yyyy-MM-dd or 'today' — if given, `period` is ignored."
}
}
},
"annotations": {
"title": "Heart rate",
"readOnlyHint": true
}
}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.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | Range end date, yyyy-MM-dd or 'today' (optional; max 100-day range). |
{
"name": "fitbit_sleep_log",
"title": "Sleep log",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
},
"endDate": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Range end date, yyyy-MM-dd or 'today' (optional; max 100-day range)."
}
}
},
"annotations": {
"title": "Sleep log",
"readOnlyHint": true
}
}Body weight log entries for a date. Fitbit REST: GET /1/user/-/body/log/weight/date/{date}.json.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
{
"name": "fitbit_weight_log",
"title": "Weight log",
"description": "Body weight log entries for a date. Fitbit REST: GET /1/user/-/body/log/weight/date/{date}.json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
}
}
},
"annotations": {
"title": "Weight log",
"readOnlyHint": true
}
}Body fat percentage log entries for a date. Fitbit REST: GET /1/user/-/body/log/fat/date/{date}.json.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
{
"name": "fitbit_body_fat_log",
"title": "Body fat log",
"description": "Body fat percentage log entries for a date. Fitbit REST: GET /1/user/-/body/log/fat/date/{date}.json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
}
}
},
"annotations": {
"title": "Body fat log",
"readOnlyHint": true
}
}Food/nutrition log for a date — logged foods and daily nutrition totals (calories, macros). Fitbit REST: GET /1/user/-/foods/log/date/{date}.json.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
{
"name": "fitbit_food_log",
"title": "Food log",
"description": "Food/nutrition log for a date — logged foods and daily nutrition totals (calories, macros). Fitbit REST: GET /1/user/-/foods/log/date/{date}.json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
}
}
},
"annotations": {
"title": "Food log",
"readOnlyHint": true
}
}Water intake log for a date. Fitbit REST: GET /1/user/-/foods/log/water/date/{date}.json.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
{
"name": "fitbit_water_log",
"title": "Water log",
"description": "Water intake log for a date. Fitbit REST: GET /1/user/-/foods/log/water/date/{date}.json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
}
}
},
"annotations": {
"title": "Water log",
"readOnlyHint": true
}
}Blood oxygen saturation (SpO2) summary for a date or range. Fitbit REST: GET /1/user/-/spo2/date/{date}[/{endDate}].json.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | Range end date, yyyy-MM-dd or 'today' (optional). |
{
"name": "fitbit_spo2",
"title": "SpO2",
"description": "Blood oxygen saturation (SpO2) summary for a date or range. Fitbit REST: GET /1/user/-/spo2/date/{date}[/{endDate}].json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
},
"endDate": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Range end date, yyyy-MM-dd or 'today' (optional)."
}
}
},
"annotations": {
"title": "SpO2",
"readOnlyHint": true
}
}Heart rate variability (HRV) summary for a date or range. Fitbit REST: GET /1/user/-/hrv/date/{date}[/{endDate}].json.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | Range end date, yyyy-MM-dd or 'today' (optional). |
{
"name": "fitbit_hrv",
"title": "HRV",
"description": "Heart rate variability (HRV) summary for a date or range. Fitbit REST: GET /1/user/-/hrv/date/{date}[/{endDate}].json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
},
"endDate": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Range end date, yyyy-MM-dd or 'today' (optional)."
}
}
},
"annotations": {
"title": "HRV",
"readOnlyHint": true
}
}Breathing (respiratory) rate summary for a date or range. Fitbit REST: GET /1/user/-/br/date/{date}[/{endDate}].json.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | Range end date, yyyy-MM-dd or 'today' (optional). |
{
"name": "fitbit_breathing_rate",
"title": "Breathing rate",
"description": "Breathing (respiratory) rate summary for a date or range. Fitbit REST: GET /1/user/-/br/date/{date}[/{endDate}].json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
},
"endDate": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Range end date, yyyy-MM-dd or 'today' (optional)."
}
}
},
"annotations": {
"title": "Breathing rate",
"readOnlyHint": true
}
}Cardio fitness score (VO2 max estimate) for a date or range. Fitbit REST: GET /1/user/-/cardioscore/date/{date}[/{endDate}].json.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | Range end date, yyyy-MM-dd or 'today' (optional). |
{
"name": "fitbit_cardio_score",
"title": "Cardio score",
"description": "Cardio fitness score (VO2 max estimate) for a date or range. Fitbit REST: GET /1/user/-/cardioscore/date/{date}[/{endDate}].json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
},
"endDate": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Range end date, yyyy-MM-dd or 'today' (optional)."
}
}
},
"annotations": {
"title": "Cardio score",
"readOnlyHint": true
}
}Skin temperature (relative to baseline) for a date or range. Fitbit REST: GET /1/user/-/temp/skin/date/{date}[/{endDate}].json.
| Parameter | Type | Description |
|---|---|---|
| date * | string | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | Range end date, yyyy-MM-dd or 'today' (optional). |
{
"name": "fitbit_skin_temperature",
"title": "Skin temperature",
"description": "Skin temperature (relative to baseline) for a date or range. Fitbit REST: GET /1/user/-/temp/skin/date/{date}[/{endDate}].json.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"date"
],
"properties": {
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Date, yyyy-MM-dd or 'today' (required)."
},
"endDate": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "Range end date, yyyy-MM-dd or 'today' (optional)."
}
}
},
"annotations": {
"title": "Skin temperature",
"readOnlyHint": true
}
}Tools for Fitbit, hosted by usefulapi.io. If the user is new or asks what this server can do, suggest requests such as: "How many steps did I take each day over the last 7 days?"; "What was my average sleep duration and efficiency last week?"; "What was my resting heart rate yesterday compared with last month?". Read-only tools never change data; ask the user before a tool that creates, changes or deletes Fitbit data. Free plan: 50 tool calls per month. Run fitbit_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run fitbit_request_feature to record the request. Paid plans: Pro (10,000 tool calls a month, $9/month or $90/year, for normal use) and Pro+ (100,000 tool calls a month, $39/month or $390/year, for automations and heavy use). A plan can be cancelled at any time and then runs to the end of the paid period, so it also suits a one-time job. When the user wants more calls or reaches the limit, run fitbit_upgrade without a plan: it returns both plans, each with a payment link for the user to open. fitbit_cancel_subscription cancels Pro at the end of the paid period.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.