Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
Descripción del creador (original en inglés)
Privacy-first, unofficial Fitbit MCP server for AI health, sleep, activity and heart-rate agents.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
FITBIT_CLIENT_ID, FITBIT_CLIENT_SECRET, FITBIT_REDIRECT_URI, FITBIT_TOKEN_PATH, FITBIT_PRIVACY_MODE, FITBIT_CACHE, FITBIT_CACHE_PATH, FITBIT_NO_CACHELos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en 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"
}
}
}
}Ejecuta esto en tu 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-unofficialCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
FITBIT_CLIENT_ID envFITBIT_REDIRECT_URI envFITBIT_TOKEN_PATH envFITBIT_PRIVACY_MODE envFITBIT_CACHE envFITBIT_CACHE_PATH envFITBIT_NO_CACHE envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub davidmosiah, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: FITBIT_CLIENT_SECRET
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.4.5) llegó al registro hace 5 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Mirobody, FHIR MCP Server, Langcare MCP FHIR
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
An MCP FHIR server written in Go for EMR systems like Epic and Cerner
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.
Default is stdio. Optional Streamable HTTP — no session id, JSON responses, loopback only:
npx -y fitbit-mcp-unofficial --http
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.
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.
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.
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.
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.
| Data | Available | Notes |
|---|---|---|
| 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 samples | conditional | Only 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 |
Start with these:
fitbit_connection_status — verify local setup before calling Fitbitfitbit_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 todayfitbit_weekly_summary — scorecard, comparison vs prior week, next-week planAuth & diagnostics
fitbit_capabilities, fitbit_agent_manifest, fitbit_privacy_audit, fitbit_cache_statusfitbit_get_auth_url, fitbit_exchange_code, fitbit_revoke_accessProfile & devices
fitbit_get_profile, fitbit_list_devicesActivity
fitbit_get_activity_day, fitbit_list_activities, fitbit_get_activityafter 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_sleepHeart & physiology (each takes a date)
fitbit_get_heart_day, fitbit_heart_series, fitbit_get_heart_intradayfitbit_get_hrv_day, fitbit_get_spo2_day, fitbit_get_breathing_rate_dayBody & nutrition (each takes a date)
fitbit_get_weight_day, fitbit_get_food_day, fitbit_get_water_dayfitbit_daily_checkin — practical daily health and activity check-infitbit_weekly_review — review trends across activity, sleep and heart contextfitbit_intraday_investigation — investigate one day's intraday heart-rate samplesfitbit://capabilities, fitbit://agent-manifestfitbit://summary/daily, fitbit://summary/weekly~/.fitbit-mcp/tokens.json with 0600 permissions and are never returned by tools.FITBIT_PRIVACY_MODE defaults to structured. Raw Fitbit JSON is opt-in via raw mode or per-call override.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
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.
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.
http://127.0.0.1:3000/callbackgit 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
The full Delx Wellness connector library:
| Provider | Package | Repo |
|---|---|---|
| WHOOP | whoop-mcp-unofficial | whoop-mcp |
| Oura | oura-mcp-unofficial | ouramcp |
| Garmin | garmin-mcp-unofficial | garminmcp |
| Strava | strava-mcp-unofficial | strava-mcp |
| Fitbit | fitbit-mcp-unofficial | [f
Solo se muestra el principio; lee el resto en el repo