FitBit MCP
Provides access to Fitbit health and fitness data including activity tracking, sleep logs, heart rate, steps, body measurements, food and water logs, lifetime statistics, device information, and earned badges through Fitbit's public API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FitBit MCP show my sleep data from yesterday"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Fitbit MCP (Model Context Protocol)
Disclaimer: This is an unofficial integration built using Fitbit's public API and is not affiliated with or endorsed by Fitbit Inc.
A Model Context Protocol (MCP) implementation for Fitbit, enabling AI assistants to access and analyze your Fitbit health and fitness data.
Usage
For JSON configuration (for use with AI assistant frameworks):
{
"command": "npx",
"args": ["-y", "fitbit-mcp", "--stdio"],
"env": {
"FITBIT_ACCESS_TOKEN": "YOUR_FITBIT_ACCESS_TOKEN"
}
}Or with arguments instead of environment variables:
{
"command": "npx",
"args": ["-y", "fitbit-mcp", "--stdio", "--fitbit-token=YOUR_FITBIT_ACCESS_TOKEN"]
}Related MCP server: fitbit-mcp
Available Tools
This MCP provides the following tools for AI assistants to access your Fitbit data:
getUserProfile: Get your Fitbit profile information
getActivities: Get activity data for a specified date
getSleepLogs: Get sleep data for a specified date
getHeartRate: Get heart rate data for a specified date and period
getSteps: Get step count for a specified date and period
getBodyMeasurements: Get weight and body fat data
getFoodLogs: Get food log data for a specified date
getWaterLogs: Get water consumption data for a specified date
getLifetimeStats: Get lifetime activity statistics
getUserSettings: Get user settings and preferences
getFloorsClimbed: Get floors climbed data
getDistance: Get distance data
getCalories: Get calories burned data
getActiveZoneMinutes: Get active zone minutes data
getDevices: Get information about connected Fitbit devices
getBadges: Get earned badges and achievements
Most tools accept optional parameters:
date: Date in YYYY-MM-DD format (defaults to today)period: Time period for data (1d, 7d, 30d, 1w, 1m)
Obtaining a Fitbit Access Token
To get a Fitbit access token:
Create an application at Fitbit Developer Portal
Set OAuth 2.0 Application Type to "Personal"
Set Callback URL to "http://localhost:3000"
After creating the application, note your Client ID and Client Secret
Use the OAuth 2.0 authorization flow to obtain an access token
For detailed instructions on OAuth authentication, see the Fitbit API Documentation.
Contributing
Contributions are welcome! Here's how you can contribute:
Fork the repository
Create your feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add some amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
Every pull request triggers a GitHub Actions workflow that verifies the build process.
Development Setup
# Clone the repository
git clone https://github.com/your-username/fitbit-mcp.git
cd fitbit-mcp
# Install dependencies
npm install
# Build the project
npm run build
# Run in development mode
npm run devRelease Process
To publish a new version to NPM:
Update the version in
package.jsonCreate a new GitHub release with a tag like
v1.0.1The GitHub Actions workflow will automatically build and publish the package to NPM
Make sure you have the NPM_TOKEN secret configured in your GitHub repository settings.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Available Tools
16 toolsgetActiveZoneMinutesD
Inputs: date, period.
getActivitiesD
Inputs: date.
getBadgesD
Inputs: no named parameters.
getBodyMeasurementsD
Inputs: date, period.
getCaloriesD
Inputs: date, period.
getDevicesD
Inputs: no named parameters.
getDistanceD
Inputs: date, period.
getFloorsClimbedD
Inputs: date, period.
getFoodLogsD
Inputs: date.
getHeartRateD
Inputs: date, period.
getLifetimeStatsD
Inputs: no named parameters.
getSleepLogsD
Inputs: date.
getStepsD
Inputs: date, period.
getUserProfileD
Inputs: no named parameters.
getUserSettingsD
Inputs: no named parameters.
getWaterLogsD
Inputs: date.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose targeting specific Fitbit data categories like heart rate, sleep, steps, badges, etc. There is no overlap or ambiguity between tools - an agent can easily select the right tool for each type of data retrieval.
All 16 tools follow a perfectly consistent 'getNoun' or 'getAdjectiveNoun' naming pattern using camelCase. The naming convention is uniform throughout the entire toolset with no deviations.
16 tools is slightly high but reasonable for a comprehensive fitness data API. Each tool represents a distinct data category that Fitbit tracks, so most tools earn their place, though some consolidation might be possible.
The toolset is severely incomplete as it only provides read-only data retrieval operations. There are no tools for creating, updating, or deleting any Fitbit data (like logging food/water, starting activities, or updating goals), which are essential for a full fitness tracking workflow.
Maintenance
Related MCP Connectors
Pace is a remote MCP server that exposes wearable and fitness data to Claude via the Model Context Protocol. It connects to Garmin, Oura, Whoop, Polar, Fitbit and 20+ devices and provides 15 tools for querying sleep, activity, recovery, and training data. Hosted on Google Cloud Run, OAuth 2.1 authentication, Streamable HTTP transport. Instructions: First you need to create an account at: https://pacetraining.co and connect your wearables. After that you can connect the remote Server via Custom Connector in Claude and OAuth 2.1 Flow startet.
MCP server for Withings health data — sleep, activity, heart, and body metrics.
Official Fibery MCP server: query and update your workspace from any AI client via OAuth.
Hosted MCP server with managed OAuth for 15+ toolkits: Google Workspace, Fitbit, Oura, Kalshi, etc.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that bridges LLMs (like Claude) with the Fitbit API, allowing the LLM to request and retrieve user health and fitness data through defined tools.1320 npm34MIT
- AlicenseAqualityFmaintenanceMCP server for the Fitbit Web API with OAuth PKCE, local cache, and trend analysis.1844 PyPI2GPL 3.0
- AlicenseBqualityBmaintenanceLocal-first MCP server that connects AI agents to your Fitbit activity, sleep, heart-rate, HRV, SpO2 and weight data.33229 npm5MIT
- AlicenseNot gradedqualityDmaintenanceThis Model Context Protocol (MCP) server connects to Garmin Connect and exposes your fitness and health data to Claude and other MCP-compatible clients.1MIT