Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Fitbit is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
17
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Fitbit profile, activity, sleep, heart rate and device data.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http usefulapi-fitbit-mcp https://fitbit.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# fitbit_get_profile, fitbit_get_devices, fitbit_daily_activity_summary and 14 more
Fitbit costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http usefulapi-fitbit-mcp https://fitbit.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The current user's Fitbit profile (name, age, gender, height, timezone, member since, avatar, etc.). Fitbit REST: GET /1/user/-/profile.json.
No parameter schema on file.
List the user's Fitbit devices/trackers (battery, last sync, version). Fitbit REST: GET /1/user/-/devices.json.
No parameter schema on file.
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 | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
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 | Required | Notes |
|---|---|---|---|
| resource | string | yes | Activity metric to fetch (required). |
| startDate | string | yes | Range start date, yyyy-MM-dd or 'today' (required). |
| endDate | string | yes | Range end date, yyyy-MM-dd or 'today' (required). |
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 | Required | Notes |
|---|---|---|---|
| period | string | yes | Goal period — 'daily' or 'weekly' (required). |
Lifetime and best-ever activity statistics (total steps, distance, floors; personal bests). Fitbit REST: GET /1/user/-/activities.json.
No parameter schema on file.
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 | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
| period | string | no | Period ending at date — used only when endDate is omitted (default '1d'). |
| endDate | string | no | Range end date, yyyy-MM-dd or 'today' — if given, period is ignored. |
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 | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | no | Range end date, yyyy-MM-dd or 'today' (optional; max 100-day range). |
Body weight log entries for a date. Fitbit REST: GET /1/user/-/body/log/weight/date/{date}.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
Body fat percentage log entries for a date. Fitbit REST: GET /1/user/-/body/log/fat/date/{date}.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
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 | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
Water intake log for a date. Fitbit REST: GET /1/user/-/foods/log/water/date/{date}.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
Blood oxygen saturation (SpO2) summary for a date or range. Fitbit REST: GET /1/user/-/spo2/date/{date}[/{endDate}].json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | no | Range end date, yyyy-MM-dd or 'today' (optional). |
Heart rate variability (HRV) summary for a date or range. Fitbit REST: GET /1/user/-/hrv/date/{date}[/{endDate}].json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | no | Range end date, yyyy-MM-dd or 'today' (optional). |
Breathing (respiratory) rate summary for a date or range. Fitbit REST: GET /1/user/-/br/date/{date}[/{endDate}].json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | no | Range end date, yyyy-MM-dd or 'today' (optional). |
Cardio fitness score (VO2 max estimate) for a date or range. Fitbit REST: GET /1/user/-/cardioscore/date/{date}[/{endDate}].json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | no | Range end date, yyyy-MM-dd or 'today' (optional). |
Skin temperature (relative to baseline) for a date or range. Fitbit REST: GET /1/user/-/temp/skin/date/{date}[/{endDate}].json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | yes | Date, yyyy-MM-dd or 'today' (required). |
| endDate | string | no | Range end date, yyyy-MM-dd or 'today' (optional). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Fitbit or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Fitbit can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.