Fitbitmcp
Connect agents to Fitbit health, sleep, activity, and heart-rate data through a privacy-first unofficial OAuth MCP server.
Overview
Fitbit MCP is a MCP server for the Build phase that exposes privacy-oriented Fitbit health, sleep, activity, and heart-rate data to AI agents via unofficial OAuth-backed tools.
What is this MCP server?
- Unofficial Fitbit MCP (v0.4.5) for health, sleep, activity, and heart-rate oriented agent tools
- OAuth with FITBIT_CLIENT_ID/SECRET; setup command prefers ~/.fitbit-mcp/config.json for secrets
- Token path configurable (default ~/.fitbit-mcp/tokens.json)
- Privacy-first posture with FITBIT_PRIVACY_MODE for controlled response shapes
- Published version 0.4.5 on npm identifier fitbit-mcp-unofficial
- Default token path ~/.fitbit-mcp/tokens.json per FITBIT_TOKEN_PATH docs
- OAuth credentials storable via setup in ~/.fitbit-mcp/config.json per package description
Community signal: 1 GitHub stars.
What problem does it solve?
Building a health-aware agent means wrestling with Fitbit OAuth, token refresh, and noisy API payloads instead of focusing on product logic.
Who is it for?
Solo builders with a Fitbit account who want agent-readable activity and sleep data for personal automation or early health-app prototypes.
Skip if: Regulated clinical products or teams that require official Fitbit partner agreements and enterprise compliance out of the box.
What do I get? / Deliverables
After OAuth setup, your agent pulls structured Fitbit metrics through MCP with secrets and tokens stored locally per the setup workflow.
- MCP-accessible Fitbit health, sleep, activity, and heart-rate queries
- Locally stored OAuth tokens and configurable privacy-shaped responses
Recommended MCP Servers
Journey fit
Wearable and health API access is integration work while you build agent features or companion apps, not launch or operate monitoring for your own SaaS errors. Fitbit OAuth, token storage, and privacy modes are classic third-party integrations for agent-tooling adjacent health copilots.
How it compares
Privacy-first wearable OAuth MCP, not a general database or Delx memory layer.
Common Questions / FAQ
Who is Fitbit MCP for?
Developers and indie builders running MCP agents who already use Fitbit and want sleep, activity, and heart-rate tools without custom API code.
When should I use Fitbit MCP?
Use it in the build integrations step when your agent or side project needs live Fitbit data and you can complete OAuth via the Fitbit developer dashboard.
How do I add Fitbit MCP to my agent?
Register a Fitbit OAuth app, install fitbit-mcp-unofficial from npm, run fitbit-mcp-server setup to store client credentials safely, finish OAuth, add stdio MCP to Claude Code or Cursor, and set FITBIT_TOKEN_PATH if you need a custom token location.