---
title: Fitbit MCP Server for AI Agents: Legacy API or Google Health?
description: Choose between legacy Fitbit Web API MCP and Google Health API v4, with the September 2026 migration deadline, fresh consent and local OAuth boundaries.
canonical: https://wellness.delx.ai/guides/fitbit-mcp-for-ai-agents
content_signal: ai-train=no, search=yes, ai-input=yes
---

# Fitbit MCP Server for AI Agents: Legacy API or Google Health?

For a new Fitbit MCP integration — including a Fitbit Air workflow — start with Google Health MCP. Google describes Google Health API as the next generation of Fitbit Web API and says the legacy API is scheduled to stop syncing Fitbit data in September 2026.

Keep `fitbit-mcp-unofficial` only for an existing legacy workflow while you migrate. Google says legacy access and refresh tokens cannot transfer: Fitbit users must re-consent through Google OAuth 2.0.

## Short answer

- New integration: run `npx -y google-health-mcp-unofficial setup` and use Google Health API v4.
- Existing legacy integration: keep `npx -y fitbit-mcp-unofficial setup` only as a migration bridge.
- Do not copy tokens between paths. Create the matching OAuth client and obtain fresh user consent.
- Run doctor, connection status, capabilities and privacy audit before requesting health records.

## How do I connect Fitbit MCP to Claude?

Install the connector, complete Fitbit OAuth, run `npx -y fitbit-mcp-unofficial doctor`, add the documented <code>mcpServers</code> block to Claude Desktop and start with `fitbit_connection_status`. For a new integration, follow the Google Health MCP path and obtain fresh consent instead of reusing legacy Fitbit tokens.

## What “Fitbit Air MCP” means

Delx Wellness does not publish a separate Air-specific connector. For Fitbit Air or another Fitbit device, use the Google Health connector for a new workflow. Google documents Google Health API as the unified access layer for current and previous Fitbit devices and Pixel watches. Actual records still depend on device support, synced account data, enabled API types and granted scopes.

## Migration method

1. Choose Google Health API for a new build; keep legacy Fitbit MCP only for an existing workflow during migration.
2. Create a Google Cloud OAuth client for Google Health or the matching Fitbit Authorization app for the legacy API.
3. Obtain fresh user consent. Legacy Fitbit tokens do not transfer to Google Health API.
4. Run `npx -y google-health-mcp-unofficial doctor` or `npx -y fitbit-mcp-unofficial doctor`, then connection status and privacy audit.
5. Compare identity, data types, summaries and missing records before cutover.

## Recommended Google Health configuration

```json
{
  "mcpServers": {
    "google_health": {
      "command": "npx",
      "args": ["-y", "google-health-mcp-unofficial"]
    }
  }
}
```

## Legacy Fitbit configuration

```json
{
  "mcpServers": {
    "fitbit": {
      "command": "npx",
      "args": ["-y", "fitbit-mcp-unofficial"]
    }
  }
}
```

## Safe first calls for Google Health

1. `google_health_connection_status`
2. `google_health_capabilities`
3. `google_health_privacy_audit`
4. `google_health_data_inventory`
5. `google_health_daily_summary`

## Data and privacy boundaries

- Activity, sleep, heart, HRV, SpO2, breathing, weight and nutrition remain device-, account-, API- and scope-dependent.
- Continuous device telemetry is not promised by either MCP connector; records appear after device/account sync.
- OAuth tokens stay local. The MCP client and language model do not receive access tokens, refresh tokens or client secrets.
- Google Health scopes are restricted and should be requested only for the records the workflow needs.
- This is technical wellness integration context, not medical advice.

## Official sources

- Google Health API overview: https://developers.google.com/health/about
- Authorization migration: https://developers.google.com/health/migration/data-access
- Data types and availability: https://developers.google.com/health/data-types

## Canonical Delx sources

- Google Health connector: https://wellness.delx.ai/connectors/google-health
- Legacy Fitbit connector: https://wellness.delx.ai/connectors/fitbit
- Connector comparison: https://wellness.delx.ai/guides/choose-wellness-mcp-connector
- Security model: https://wellness.delx.ai/security

Delx Wellness, fitbit-mcp-unofficial and google-health-mcp-unofficial are not affiliated with Google, Fitbit or Alphabet.