io.github.davidmosiah/fitbitmcp MCP Server
io.github.davidmosiah/fitbitmcp
What this kind of tool is for
- Hand your agent a structured way to call a model or an inference API.
- Compare outputs from two different providers on the same prompt.
- Wire retrieval, embeddings, or generation into an existing agent workflow.
How to compare servers like this
- Provider coverage:
- Match the tool's supported providers and models to the ones your project uses.
- Cost exposure:
- Model-backed tools spend real API budget; check how usage and limits are configured.
- Maintenance signal:
- The provider landscape shifts weekly; prefer tools updated within the last few months.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the io.github.davidmosiah/fitbitmcp MCP server?
Privacy-first, unofficial Fitbit MCP server for AI health, sleep, activity and heart-rate agents.
How to install io.github.davidmosiah/fitbitmcp
Copy-paste configuration for popular MCP clients.
FITBIT_CLIENT_IDFitbit OAuth client ID. Optional when configured with fitbit-mcp-server setup.
FITBIT_CLIENT_SECRETsecretFitbit 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_URIRedirect URI configured in the Fitbit Developer Dashboard. Optional when configured with fitbit-mcp-server setup.
FITBIT_TOKEN_PATHOptional local path for OAuth tokens. Defaults to ~/.fitbit-mcp/tokens.json.
FITBIT_PRIVACY_MODEOptional payload mode: summary, structured, or raw. Defaults to structured. raw means full Fitbit API payloads, not continuous 24/7 raw sensor telemetry.
FITBIT_CACHEOptional SQLite cache toggle. Set to true or sqlite to enable.
FITBIT_CACHE_PATHOptional local SQLite cache path. Defaults to ~/.fitbit-mcp/cache.sqlite.
FITBIT_NO_CACHESet 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.
{
"mcpServers": {
"fitbitmcp": {
"command": "npx",
"args": [
"-y",
"fitbit-mcp-unofficial"
],
"env": {
"FITBIT_CLIENT_ID": "<YOUR_FITBIT_CLIENT_ID>",
"FITBIT_CLIENT_SECRET": "<YOUR_FITBIT_CLIENT_SECRET>",
"FITBIT_REDIRECT_URI": "<YOUR_FITBIT_REDIRECT_URI>",
"FITBIT_TOKEN_PATH": "<YOUR_FITBIT_TOKEN_PATH>",
"FITBIT_PRIVACY_MODE": "<YOUR_FITBIT_PRIVACY_MODE>",
"FITBIT_CACHE": "<YOUR_FITBIT_CACHE>",
"FITBIT_CACHE_PATH": "<YOUR_FITBIT_CACHE_PATH>",
"FITBIT_NO_CACHE": "<YOUR_FITBIT_NO_CACHE>"
}
}
}
}Related MCP servers

Privacy-first unofficial Garmin Connect MCP for AI health, sleep, activity & recovery agents.
Dry-run-first Google Ads search-term intent analyzer and negative-keyword MCP for agents.
Unofficial Google Ads MCP for campaigns, keywords, budgets, and gated mutations.
Privacy-first MCP server for Google Health API v4 data—Fitbit, Pixel Watch, and partners—with local OAuth and zero token exposure.
Agent-readiness scorecard for any MCP server: 10 checks, 0-100 score, actionable findings.

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