How do I connect Fitbit MCP Server to Claude?

Run `claude mcp add fitbit-mcp -- uvx fitbit-mcp` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.

Is Fitbit MCP Server free?

The listed licence is GPL-3.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.

What can Fitbit MCP Server do?

Fitbit MCP Server documents 6 tools to the agent, including end_date, exercise_type, fitbit_sync. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

Fitbit MCP

Unclaimed

by partymola

MCP server for the Fitbit Web API with OAuth PKCE, local SQLite cache, and trend analysis

Set up this server

Compare servers My Stack

01 / Choose your client

02 / Before you connect

Authentication is not specified. Check the project instructions before connecting.

Install the runtime required by the project and make it available to your client.

Project instructionsEnvironment variable names (optional)

Use names from the project instructions, separated by commas. Enter names only, never secret values.

03 / Add the configuration

Source: generated from public install instructions

claude mcp add --transport stdio 'fitbit-mcp' -- 'uvx' 'fitbit-mcp'

Run in your terminal after replacing any placeholders.

04 / Check it in your client

Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.

claudefitbitfitbit-apimcpmcp-servermodel-context-protocoloauthquantified-self

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

6 of 6 tools

Documented tools (6)

From project documentation. A server handshake does not verify each tool’s description or behavior.

end_date

End date as YYYY-MM-DD. Default: today.

exercise_type

Filter by activity name (case-insensitive substring match), e.g. "cycling", "walk", "run". Default: all types.

fitbit_sync

Syncs data from the Fitbit API to the local SQLite cache. Query tools call this automatically on first use of the day, so explicit calls are only needed for longer history or forced refresh.

fitbit_trends

Aggregated trend analysis from cached data.

live

If true, fetch from Fitbit API instead of cache (bypasses auto-sync).

start_date

Start date as YYYY-MM-DD, YYYY-MM, or 30d (relative). Default: last 30 days.

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Fitbit MCP Server

How do I connect Fitbit MCP Server to Claude?: Run `claude mcp add fitbit-mcp -- uvx fitbit-mcp` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
Is Fitbit MCP Server free?: The listed licence is GPL-3.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Fitbit MCP Server do?: Fitbit MCP Server documents 6 tools to the agent, including end_date, exercise_type, fitbit_sync. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.