Google Health Fitbit
Connect your Fitbit / Pixel Watch data to any AI assistant via MCP. Read-only MCP server for the Google Health API. Your health data → any AI assistant, tokens never leave your machine.
{ "mcpServers": { "berkkilicoglu-google-health-fitbit-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "GOOGLE_HEALTH_CLIENT_ID": "<value>", "GOOGLE_HEALTH_CLIENT_SECRET": "<secret>", "GOOGLE_HEALTH_REDIRECT_URI": "<value>", "GOOGLE_HEALTH_TOKEN_PATH": "<value>", "GOOGLE_HEALTH_PRIVACY_MODE": "<value>", "GOOGLE_HEALTH_CACHE": "<value>", "GOOGLE_HEALTH_CACHE_PATH": "<value>", "GOOGLE_HEALTH_NO_CACHE": "<value>" } } }}.cursor/mcp.jsonMCP server
- Transport
- stdio
- Status
- Local
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
Local command
npx -y [email protected]Credentials from the publisher
- GOOGLE_HEALTH_CLIENT_ID — Google Cloud OAuth client ID for Google Health API. Optional when configured with google-health-fitbit-mcp-server setup.
- GOOGLE_HEALTH_CLIENT_SECRET — Google Cloud OAuth client secret. Prefer google-health-fitbit-mcp-server setup so this secret is stored in ~/.google-health-mcp/config.json instead of MCP client config.
- GOOGLE_HEALTH_REDIRECT_URI — Redirect URI configured in the Google Cloud OAuth client. Optional when configured with google-health-fitbit-mcp-server setup.
- GOOGLE_HEALTH_TOKEN_PATH — Optional local path for OAuth tokens. Defaults to ~/.google-health-mcp/tokens.json.
- GOOGLE_HEALTH_PRIVACY_MODE — Optional payload mode: summary, structured, or raw. Defaults to structured. raw means full Google Health API payloads, not continuous 24/7 raw sensor telemetry.
- GOOGLE_HEALTH_CACHE — Optional SQLite cache toggle. Set to true or sqlite to enable.
- GOOGLE_HEALTH_CACHE_PATH — Optional local SQLite cache path. Defaults to ~/.google-health-mcp/cache.sqlite.
- GOOGLE_HEALTH_NO_CACHE — Set to true to bypass the in-memory HTTP response cache (60s TTL for GET only). POST/PUT/DELETE and 4xx/5xx responses are never cached regardless.
Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
shClaude Code
GOOGLE_HEALTH_CLIENT_ID=<value> GOOGLE_HEALTH_CLIENT_SECRET=<secret> GOOGLE_HEALTH_REDIRECT_URI=<value> GOOGLE_HEALTH_TOKEN_PATH=<value> GOOGLE_HEALTH_PRIVACY_MODE=<value> GOOGLE_HEALTH_CACHE=<value> GOOGLE_HEALTH_CACHE_PATH=<value> GOOGLE_HEALTH_NO_CACHE=<value> claude mcp add berkkilicoglu-google-health-fitbit-mcp -- npx -y google-health-fitbit-mcp@1.0.2Run in a terminal.
jsonClaude Desktop
{ "mcpServers": { "berkkilicoglu-google-health-fitbit-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "GOOGLE_HEALTH_CLIENT_ID": "<value>", "GOOGLE_HEALTH_CLIENT_SECRET": "<secret>", "GOOGLE_HEALTH_REDIRECT_URI": "<value>", "GOOGLE_HEALTH_TOKEN_PATH": "<value>", "GOOGLE_HEALTH_PRIVACY_MODE": "<value>", "GOOGLE_HEALTH_CACHE": "<value>", "GOOGLE_HEALTH_CACHE_PATH": "<value>", "GOOGLE_HEALTH_NO_CACHE": "<value>" } } }}claude_desktop_config.json
Local · npmPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchServer facts
Local- Transport
- stdio
- License
- MIT
- API key
- GOOGLE_HEALTH_CLIENT_ID, GOOGLE_HEALTH_CLIENT_SECRET, GOOGLE_HEALTH_REDIRECT_URI, GOOGLE_HEALTH_TOKEN_PATH, GOOGLE_HEALTH_PRIVACY_MODE, GOOGLE_HEALTH_CACHE, GOOGLE_HEALTH_CACHE_PATH, GOOGLE_HEALTH_NO_CACHE
- Last checked
- 2026-10-26
- Stars
- 19
- Tools
- —
- Uptime
- —
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Questions
How do I install Google Health Fitbit?
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does Google Health Fitbit need an API key?
The publisher lists these environment variables: GOOGLE_HEALTH_CLIENT_ID, GOOGLE_HEALTH_CLIENT_SECRET, GOOGLE_HEALTH_REDIRECT_URI, GOOGLE_HEALTH_TOKEN_PATH, GOOGLE_HEALTH_PRIVACY_MODE, GOOGLE_HEALTH_CACHE, GOOGLE_HEALTH_CACHE_PATH, GOOGLE_HEALTH_NO_CACHE.
What transport does Google Health Fitbit use?
Google Health Fitbit runs locally over stdio.
When was Google Health Fitbit last checked?
Last checked 2026-10-26. Connect your Fitbit / Pixel Watch data to any AI assistant via MCP. Read-only MCP server for the Google Health API. Your health data → any AI assistant, tokens never leave your machine.
From the publisher
Documentation
README is not crawled yet. Open the repository