Model Context Protocol (MCP) server for accessing Fitbit health and fitness data. Connect AI assistants like Claude to your Fitbit data for
Connect MCP Fitbit to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Model Context Protocol (MCP) server for accessing Fitbit health and fitness data. Connect AI assistants like Claude to your Fitbit data for personalized health insights. The mcp fitbit mcp server is what makes that connection.
Give your AI assistant access to your Fitbit data for personalized health insights, trend analysis, and automated tracking. Works with Claude Desktop and other MCP-compatible AI tools.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
get_weight — Weight data over time periodsget_sleep_by_date_range — Sleep logs for date range (max 100 days)get_exercises — Activity/exercise logs after dateget_daily_activity_summary — Daily activity summary with goalsget_activity_goals — User's activity goals (daily/weekly)get_activity_timeseries — Activity time series data (max 30 days)get_azm_timeseries — Active Zone Minutes time series (max 1095 days)get_heart_rate — Heart rate for time periodget_heart_rate_by_date_range — Heart rate for date range (max 1 year)get_food_log — Complete nutrition data for a dayget_nutrition — Individual nutrient over timeget_nutrition_by_date_range — Individual nutrient for date rangemcp-fitbit on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: FITBIT_CLIENT_ID, FITBIT_CLIENT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Fitbit's toolset — get_weight, get_sleep_by_date_range, get_exercises and 10 more — is a fair guide to whether it matches your workflow. It is maintained by TheDigitalNinja; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_weight | Weight data over time periods |
| get_sleep_by_date_range | Sleep logs for date range (max 100 days) |
| get_exercises | Activity/exercise logs after date |
| get_daily_activity_summary | Daily activity summary with goals |
| get_activity_goals | User's activity goals (daily/weekly) |
| get_activity_timeseries | Activity time series data (max 30 days) |
| get_azm_timeseries | Active Zone Minutes time series (max 1095 days) |
| get_heart_rate | Heart rate for time period |
| get_heart_rate_by_date_range | Heart rate for date range (max 1 year) |
| get_food_log | Complete nutrition data for a day |
| get_nutrition | Individual nutrient over time |
| get_nutrition_by_date_range | Individual nutrient for date range |
| get_profile | User profile information |
{
"mcpServers": {
"fitbit": {
"command": "mcp-fitbit",
"args": []
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| FITBIT_CLIENT_ID | Configuration value read at startup. | Optional |
| FITBIT_CLIENT_SECRET | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.