Related Servers

Several tool clusters blur together: fitbit_data_inventory, fitbit_capabilities, and fitbit_agent_manifest all describe supported data, privacy, and guidance; fitbit_connection_status and fitbit_privacy_audit both inspect local state. The confusing fitbit_get_profile vs fitbit_profile_get pair is especially risky because one returns Fitbit profile data and the other returns the Delx wellness profile.

All tools share the fitbit_ prefix and snake_case, but the naming conventions are mixed: verb_noun forms like fitbit_get_activity_day coexist with noun-only names like fitbit_daily_summary, and reversed noun_verb forms like fitbit_profile_get and fitbit_profile_update. The near-match between fitbit_get_profile and fitbit_profile_get highlights the inconsistency and increases misselection risk.

33 tools is too many for a well-scoped MCP server. A large portion are meta, setup, and status tools—inventory, manifest, capabilities, quickstart, demo, connection status, cache status, and privacy audit—that overlap and could be consolidated without losing functional coverage.

The server covers the Fitbit wellness domain well: OAuth lifecycle, profile, devices, activity, sleep, heart rate, HRV, breathing rate, SpO2, weight, food, water, plus daily/weekly summaries and a shared wellness profile. Minor gaps exist such as lack of sleep-log-by-id detail or explicit token refresh, but core read-only Fitbit workflows have no dead ends.