Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Fitbitmcp

by davidmosiahversion 0.4.5i★ –iRuns on your computer
Registry nameio.github.davidmosiah/fitbitmcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Clinics & health
  • You need to fill in: FITBIT_CLIENT_SECRET

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: FITBIT_CLIENT_ID, FITBIT_CLIENT_SECRET, FITBIT_REDIRECT_URI, FITBIT_TOKEN_PATH, FITBIT_PRIVACY_MODE, FITBIT_CACHE, FITBIT_CACHE_PATH, FITBIT_NO_CACHE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "fitbitmcp": {
      "command": "npx",
      "args": [
        "-y",
        "fitbit-mcp-unofficial"
      ],
      "env": {
        "FITBIT_CLIENT_ID": "your-value",
        "FITBIT_CLIENT_SECRET": "your-value",
        "FITBIT_REDIRECT_URI": "your-value",
        "FITBIT_TOKEN_PATH": "your-value",
        "FITBIT_PRIVACY_MODE": "your-value",
        "FITBIT_CACHE": "your-value",
        "FITBIT_CACHE_PATH": "your-value",
        "FITBIT_NO_CACHE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add fitbitmcp --env FITBIT_CLIENT_ID=your-value --env FITBIT_CLIENT_SECRET=your-value --env FITBIT_REDIRECT_URI=your-value --env FITBIT_TOKEN_PATH=your-value --env FITBIT_PRIVACY_MODE=your-value --env FITBIT_CACHE=your-value --env FITBIT_CACHE_PATH=your-value --env FITBIT_NO_CACHE=your-value -- npx -y fitbit-mcp-unofficial

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "fitbitmcp": {
      "command": "npx",
      "args": [
        "-y",
        "fitbit-mcp-unofficial"
      ],
      "env": {
        "FITBIT_CLIENT_ID": "your-value",
        "FITBIT_CLIENT_SECRET": "your-value",
        "FITBIT_REDIRECT_URI": "your-value",
        "FITBIT_TOKEN_PATH": "your-value",
        "FITBIT_PRIVACY_MODE": "your-value",
        "FITBIT_CACHE": "your-value",
        "FITBIT_CACHE_PATH": "your-value",
        "FITBIT_NO_CACHE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "fitbitmcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "fitbit-mcp-unofficial"
      ],
      "env": {
        "FITBIT_CLIENT_ID": "your-value",
        "FITBIT_CLIENT_SECRET": "your-value",
        "FITBIT_REDIRECT_URI": "your-value",
        "FITBIT_TOKEN_PATH": "your-value",
        "FITBIT_PRIVACY_MODE": "your-value",
        "FITBIT_CACHE": "your-value",
        "FITBIT_CACHE_PATH": "your-value",
        "FITBIT_NO_CACHE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • FITBIT_CLIENT_ID env
    Fitbit OAuth client ID. Optional when configured with fitbit-mcp-server setup.
  • FITBIT_CLIENT_SECRET secret env
    Fitbit OAuth client secret. Prefer fitbit-mcp-server setup so this secret is stored in ~/.fitbit-mcp/config.json instead of MCP client config.
  • FITBIT_REDIRECT_URI env
    Redirect URI configured in the Fitbit Developer Dashboard. Optional when configured with fitbit-mcp-server setup.
  • FITBIT_TOKEN_PATH env
    Optional local path for OAuth tokens. Defaults to ~/.fitbit-mcp/tokens.json.
  • FITBIT_PRIVACY_MODE env
    Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full Fitbit API payloads, not continuous 24/7 raw sensor telemetry.
  • FITBIT_CACHE env
    Optional SQLite cache toggle. Set to true or sqlite to enable.
  • FITBIT_CACHE_PATH env
    Optional local SQLite cache path. Defaults to ~/.fitbit-mcp/cache.sqlite.
  • FITBIT_NO_CACHE env
    Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account davidmosiah, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Clinics & healthi

  • More stars than 0% of the other 869 servers in this category
  • Published to the registry more recently than 14% of the other 869 servers in this category
  • Basic checks equal to or better than 100% of the other 869 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Fitbitmcp safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: FITBIT_CLIENT_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.5) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Mirobody, FHIR MCP Server, Langcare MCP FHIR

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Mirobody

by thetahealth

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

Runs on your computer★ 1,408Apache-2.0Updated 5 days ago
Install

MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications

Runs on your computer★ 137Apache-2.0Updated 9 days ago
Install

An MCP FHIR server written in Go for EMR systems like Epic and Cerner

Runs on your computer★ 70MITUpdated 9 months ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Fitbit MCP

Give your AI agent your Fitbit activity, sleep, heart and HRV data — locally.

Local-first MCP server — tokens never leave your machine .

⚡ One-command install with Delx Wellness for Hermes:

npx -y delx-wellness-hermes setup — preconfigures this connector and the other 8 in a dedicated Hermes profile.

Or wire it standalone into Claude Desktop / Cursor / ChatGPT Desktop — see the install section below.


HTTP (v2 stateless)

Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:

npx -y fitbit-mcp-unofficial --http

GET http://127.0.0.1:3000/health

POST http://127.0.0.1:3000/mcp (sessionless)

Env: FITBIT_MCP_HOST, FITBIT_MCP_PORT, FITBIT_MCP_TRANSPORT=http.

Local-first MCP server that connects AI agents to your Fitbit activity, sleep, heart-rate, HRV, SpO2 and weight data.

Unofficial project. Not affiliated with, endorsed by or supported by Fitbit or Google. Use this only with your own Fitbit account and in line with the Fitbit Web API terms.

Platform migration risk: Fitbit is migrating to the Google Health API. OAuth, base URL, scopes and reconnection flows may change in 2026. Treat any breakage as platform drift and check the Fitbit Web API docs before reporting it as a bug.

Built by David Mosiah for people who use Claude, Cursor, Hermes, OpenClaw or other MCP-compatible agents to think about activity, sleep and heart context — without copy-pasting numbers from the Fitbit app.

Part of Delx Wellness, a registry of local-first wellness MCP connectors.

If this connector helps your agent workflow, please star the repo. Stars make the project easier for other AI builders to discover and help Delx keep shipping local-first wellness infrastructure.

Why this exists

Fitbit (now under Google) has years of wearable data — daily activity, sleep stages, intraday heart-rate, HRV, SpO2, breathing rate, weight, food and water logs. But its API uses OAuth 2.0 with per-scope authorization and intraday access that varies by app, and the platform is mid-migration to the Google Health API.

This package handles the OAuth dance locally, normalizes responses, and exposes Fitbit through the Model Context Protocol. Tokens never leave your machine. Privacy-mode defaults keep raw payloads opt-in.

Setup in 60 seconds

You'll need a Fitbit app (create one here) with redirect URI http://127.0.0.1:3000/callback.

npx -y fitbit-mcp-unofficial setup    # interactive: paste client id + secret

npx -y fitbit-mcp-unofficial auth # opens browser, captures the OAuth code npx -y fitbit-mcp-unofficial doctor # verifies you're ready

Recommended scopes:

activity heartrate profile settings sleep weight nutrition

Then add this to your MCP client config:

{

"mcpServers": { "fitbit": { "command": "npx", "args": ["-y", "fitbit-mcp-unofficial"] } } }

For Claude Desktop, run setup --client claude and the snippet is written for you.

Try it with your agent

Three things to ask first:

Use fitbit_connection_status to check setup, then run fitbit_daily_summary.

Give me a 5-line operating brief for today.

Call fitbit_weekly_summary with response_format=json. Identify my biggest

sleep/activity bottleneck and give me a next-week plan.

Use the fitbit_intraday_investigation prompt for date=today, detail_level=1min.

Don't claim anything Fitbit can't actually prove.

Data availability

This package uses the official Fitbit Web API. When this README says raw, it means the upstream Fitbit JSON for a supported endpoint — not raw device sensor streams.

DataAvailableNotes
Daily activity (steps, calories, distance, zones)✓Standard activity summaries
Activity logs✓Logged workouts
Sleep + sleep stages✓When Fitbit returns stage data
Resting heart rate + daily heart-rate zones✓All scored days
Intraday heart-rate samplesconditionalOnly when the Fitbit app/API access permits intraday
HRV (overnight)✓When supported by device/account
SpO2 (overnight)✓When supported by device/account
Breathing rate✓When supported by device/account
Weight + body composition✓When logged
Food + water logs✓When logged
Continuous device telemetry—Not exposed by Fitbit's public API

Tools

Start with these:

  • fitbit_connection_status — verify local setup before calling Fitbit
  • fitbit_data_inventory — inventory supported data domains, scopes, privacy modes and recommended first calls without calling Fitbit APIs.
  • fitbit_daily_summary — readiness, activity, sleep and heart context for today
  • fitbit_weekly_summary — scorecard, comparison vs prior week, next-week plan

Auth & diagnostics

  • fitbit_capabilities, fitbit_agent_manifest, fitbit_privacy_audit, fitbit_cache_status
  • fitbit_get_auth_url, fitbit_exchange_code, fitbit_revoke_access

Profile & devices

  • fitbit_get_profile, fitbit_list_devices

Activity

  • fitbit_get_activity_day, fitbit_list_activities, fitbit_get_activity
  • List calls accept either after or before, matching Fitbit's mutually exclusive cursor contract. Offset ISO inputs retain their written calendar date and invalid cursors fail before HTTP.

Sleep

  • fitbit_get_sleep_day, fitbit_list_sleep

Heart & physiology (each takes a date)

  • fitbit_get_heart_day, fitbit_heart_series, fitbit_get_heart_intraday
  • fitbit_get_hrv_day, fitbit_get_spo2_day, fitbit_get_breathing_rate_day

Body & nutrition (each takes a date)

  • fitbit_get_weight_day, fitbit_get_food_day, fitbit_get_water_day

Prompts

  • fitbit_daily_checkin — practical daily health and activity check-in
  • fitbit_weekly_review — review trends across activity, sleep and heart context
  • fitbit_intraday_investigation — investigate one day's intraday heart-rate samples

Resources

  • fitbit://capabilities, fitbit://agent-manifest
  • fitbit://summary/daily, fitbit://summary/weekly

Privacy & security

  • OAuth tokens are stored in ~/.fitbit-mcp/tokens.json with 0600 permissions and are never returned by tools.
  • The server never prints access or refresh tokens.
  • FITBIT_PRIVACY_MODE defaults to structured. Raw Fitbit JSON is opt-in via raw mode or per-call override.
  • Structured mode preserves complete upstream physiological records and response metadata while removing GPS and secret-bearing fields.
  • Health data is sensitive — do not paste raw payloads publicly.
  • This is not medical advice. The server exposes user-authorized data for personal AI workflows, not diagnosis or treatment.

Configuration

setup writes most of these into ~/.fitbit-mcp/config.json (0600). Manual env override is supported:

FITBIT_CLIENT_ID=…

FITBIT_CLIENT_SECRET=… FITBIT_REDIRECT_URI=http://127.0.0.1:3000/callback

Optional

FITBIT_SCOPES="activity heartrate profile settings sleep weight nutrition" FITBIT_PRIVACY_MODE=structured # summary | structured | raw FITBIT_CACHE=sqlite # retained setting; authenticated payload cache/fallback disabled

Authenticated responses bypass both payload caches and offline fallback. Existing SQLite entries are preserved, not inspected or removed by cache status; errors propagate. Anonymous HTTP caching remains available.

Hermes / remote setup

npx -y fitbit-mcp-unofficial setup --client hermes --no-auth

npx -y fitbit-mcp-unofficial auth # run locally if browser auth is needed npx -y fitbit-mcp-unofficial doctor --client hermes hermes mcp test fitbit

After Hermes config changes, use /reload-mcp or hermes mcp test fitbit. Don't restart the gateway for normal data access.

If browser OAuth has to happen on a different machine than Hermes, run auth locally and copy ~/.fitbit-mcp/tokens.json to the server with chmod 600.

Requirements

  • Node.js 20+
  • A Fitbit app at https://dev.fitbit.com/apps with redirect URI http://127.0.0.1:3000/callback
  • Intraday heart-rate access requires the Fitbit app to be approved for intraday data (varies per app)

Development

git clone https://github.com/davidmosiah/fitbit-mcp.git

cd fitbit-mcp npm install npm test npm run build

Test with MCP Inspector:

npx @modelcontextprotocol/inspector node dist/index.js

Links

See also

The full Delx Wellness connector library:

| Fitbit | fitbit-mcp-unofficial | [f

Only the beginning is shown; read the rest in the repo

Ask PopNx