Migration guide · two MCP paths

Fitbit MCP server for AI agents

Choose between the legacy Fitbit Web API connector and the next-generation Google Health API path without losing the privacy boundary or migration deadline.

Short answer

For a new Fitbit MCP integration — including a Fitbit Air workflow — start with Google Health MCP. Google calls Google Health API the next generation of Fitbit Web API and schedules the legacy API to stop syncing Fitbit data in September 2026. Keep fitbit-mcp-unofficial only for an existing legacy workflow while you migrate and obtain fresh user consent.

The official migration changes the decision

Google says legacy Fitbit access and refresh tokens cannot move to Google Health API. Fitbit users must re-consent through Google OAuth 2.0. Treat the September 2026 date as a migration deadline, not a reason to silently swap credentials or APIs.

Google Health API overview Official authorization migration

New integration

Choose Google Health MCP

Use Google Health API v4 for Fitbit and Pixel Watch data, reconciled streams and the post-migration OAuth model.

npx -y google-health-mcp-unofficial setup

Google OAuth 2.0 through a Google Cloud project.
Fitbit and Pixel device records where supported.
Restricted health scopes and explicit user consent.
Read-only MCP connector during the API launch window.

Open connector specification

Existing integration

Maintain legacy Fitbit MCP temporarily

Use the legacy connector only when an existing Fitbit Web API workflow must keep running during a planned migration.

npx -y fitbit-mcp-unofficial setup

Fitbit Authorization and legacy Web API endpoints.
Existing activity, sleep, heart, body and nutrition tools.
No token transfer to Google Health API.
Cutover required before the documented shutdown.

Open connector specification

What “Fitbit Air MCP” means here

Delx Wellness does not publish a separate Air-specific MCP 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 capabilities, synced account data, enabled API types and granted scopes.

Read Google Health data availability

Migration method

Move without confusing identity, consent or data gaps

1
Choose the API generation
Use Google Health API for a new build. Keep legacy Fitbit MCP only for an existing workflow while you plan migration.
2
Create the matching OAuth client
Legacy Fitbit apps use Fitbit Authorization. Google Health apps use a Google Cloud project, Google OAuth 2.0 and restricted health scopes.
3
Ask for fresh consent
Do not copy legacy tokens. Users must re-consent to the Google Health integration because tokens do not transfer.
4
Verify the connector before records
Run doctor, connection status, capabilities and privacy audit before asking an agent for a daily or weekly summary.
5
Compare output before cutover
Check identity, available data types, summaries and missing records while the legacy workflow still exists; disclose device and scope gaps.

Google Health MCP — recommended for new work

terminal

npx -y google-health-mcp-unofficial setup
npx -y google-health-mcp-unofficial doctor

mcp-client.json

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

Legacy Fitbit MCP — migration bridge

terminal

npx -y fitbit-mcp-unofficial setup
npx -y fitbit-mcp-unofficial doctor

mcp-client.json

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

What an agent can request after consent

Activity and movement

Steps, distance, calories, active minutes and supported workout records.

Sleep

Sleep sessions, stages and summaries when the account and device expose them.

Health metrics

Heart rate, HRV, SpO2, breathing, weight and related metrics remain device-, API- and scope-dependent.

Google Health streams

Data points, daily rollups and reconciled streams where Google Health API supports the data type.

Continuous device telemetry is not a promise of either MCP connector. Data appears after the device and account sync, and availability changes by device, scope, API generation and account state.

Safe first calls — 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

Privacy boundary

OAuth tokens stay local for both paths. The MCP client and language model do not receive access tokens, refresh tokens or client secrets. Request only the scopes and records needed for the current wellness purpose.

Fitbit MCP questions

What is a Fitbit MCP server?

A Fitbit MCP server lets an MCP-compatible AI agent request user-authorized activity, sleep, heart, body and nutrition records through named tools. Delx Wellness documents both the legacy Fitbit Web API connector and the next-generation Google Health API connector.

How do I connect Fitbit MCP to Claude?

Install the connector, complete Fitbit OAuth, run the doctor command, add the documented mcpServers 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.

Which MCP connector should a new Fitbit integration use?

Use the Google Health MCP path for a new integration. 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.

Is there a separate Fitbit Air MCP connector?

No separate Fitbit Air connector is required in Delx Wellness. Google documents Google Health API as the access layer for current and previous Fitbit devices and Pixel watches, with actual records depending on device support, account data and granted scopes.

Can existing Fitbit OAuth tokens move to Google Health API?

No. Google's migration documentation says Fitbit users must re-consent because legacy access and refresh tokens cannot be transferred to Google Health API.

Does an AI model receive the Fitbit or Google OAuth token?

No. Both local connectors keep OAuth tokens on the machine running the MCP server. The model receives bounded MCP results, not access tokens, refresh tokens or client secrets.

Continue with the canonical sources

Google Health MCP specification Legacy Fitbit MCP specification Official migration and authorization guide Machine-readable Markdown

Delx Wellness, fitbit-mcp-unofficial and google-health-mcp-unofficial are not affiliated with Google, Fitbit or Alphabet. This guide provides technical integration context, not medical advice.