fitbitmcp
fitbitmcp is an MCP server published by davidmosiah, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does fitbitmcp support the current MCP specification (2026-07-28)?
Not yet confirmed. fitbitmcp is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is fitbitmcp a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for fitbitmcp (as of 2026-08-20).
How do I connect to fitbitmcp?
fitbitmcp is available via the package npm:fitbit-mcp-unofficial, the official MCP Registry under io.github.davidmosiah/fitbitmcp, the source repository at https://github.com/davidmosiah/fitbit-mcp. Authentication: unknown. Transports: stdio.
Does fitbitmcp support MCP revision 2025-11-25?
Yes. fitbitmcp supports MCP revision 2025-11-25 (checked 2026-08-20).
Does fitbitmcp support MCP revision 2026-07-28?
No. fitbitmcp was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were fitbitmcp's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Privacy-first, unofficial Fitbit MCP server for AI health, sleep, activity and heart-rate agents.
Which MCP spec revisions does fitbitmcp support?
fitbitmcp has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is fitbitmcp?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for fitbitmcp
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 1
- Forks
- 1
- Last pushed
- (48 days ago)
- Created
- Open issues
- 0
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- None detected
- Security policy
- Present
Declared topics: ai-agents, claude, claude-mcp, fitbit, fitness, health, health-data, local-first, mcp, mcp-server, model-context-protocol, quantified-self, recovery, sleep, typescript, wearables — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.6.2- Last published
- First published
- Releases
- 20
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 5
- Unpacked size
- 747 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.davidmosiah/fitbitmcp at version 0.4.5 - lists package npm:fitbit-mcp-unofficial and repository https://github.com/davidmosiah/fitbit-mcp - accessed
- npm registry metadata for fitbit-mcp-unofficial at published version 0.6.2, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed