Skip to the content

Fitbit for agents

Other. MCP servers, the command line and skills for connecting an agent to Fitbit.

Build an agent with Fitbit

Official server
none identified
Sourced servers by others
2
Command line
none curated
Vendor skills
none

Official server

We have not identified a server published by Fitbit's owner in the MCP Registry (read ). One may exist, in the registry under a name we have not matched or outside it. The servers below are by other publishers.

How it is reached

As Fitbit's vendor states it, read from its own page on the day given.

  • Through its API. Each user signs in to their own account. The vendor says it ended on . The vendor's page, read .

Servers by other publishers

3 servers for Fitbit that name a public repository or a package, or whose tools we could read. Anyone can publish one, and we have not read their code: check the publisher and the source before giving one a credential.

In this order: live servers before deprecated ones, first-party first, a known vulnerability last, then more downloads, then a more recent push, then by name. There is no score, and the number of tools is not part of the order: fewer is not better. Tools are what a server listed to a client with no credential, or what its package listed when run with no network, downloads are from npm and pypistats, the last push from GitHub and vulnerabilities from OSV; a server's own page has the day each was read, and "not read" means we have no figure, not that there is none. See how this directory is made.

ServerPublisherReachToolsDownloads a weekLast pushVulnerabilities
io.github.BerkKilicoglu/google-health-fitbit-mcpSourcednpmnot read130not readnone known
Fitbit MCP by usefulapiio.usefulapi/fitbitInspectedremote17not readnot readnot checked
io.github.partymola/fitbit-mcpSourcedDeprecatedPyPInot read52not readnone known

Changes for Fitbit

None in the last 30 days. The log began on , and nothing older was recorded.

A change is a difference between two readings of public records, not a review. Fitbit in the log · How the log is made · Fitbit's Atom feed

A server is listed for Fitbit when we have named it as the system's official server, when its registry title or the last part of its registry name names Fitbit as whole words, or when it is published at Fitbit's own domain. See how this directory is made.

Built from agent catalog version 2026-11-18.1 of , from the MCP Registry as read on . A listing here is not an endorsement: anyone can publish a server, and we have not read its code. Names, descriptions and addresses are the publisher's own. See how this directory is made, and tell us about a wrong entry through the contact page.