"A server to manage API rate limiting based on requests per minute" matching MCP servers:

Enables AI clients to access live heart rate readings, recent history, and events from sources such as Pulsoid, HypeRate, Bluetooth, OSC, HTTP pushes, or text files, while optionally pushing updates to Discord and JSON webhooks.

Enables an MCP client to read and write a personal Garmin Connect account: activities with per-set strength detail, daily health metrics (sleep, HRV, stress, steps, readiness), planned and completed workouts, and weigh-ins with body composition. It also logs finished strength sessions and body-composition readings as FIT files so they appear in Garmin Connect like natively recorded ones.

Enables retrieval of InBody body composition data including profile, scan history, and full metrics via MCP tools.

MCP server for Cronometer nutrition tracking, enabling food diary management, nutrition data retrieval, food search, and biometric tracking via Cronometer's mobile REST API.

MCP server for Cronometer nutrition tracking using the mobile API. Enables food logging, nutrition data retrieval, diary management, and fasting tracking.

A read-only MCP server that lets AI assistants query a user's own training, recovery, sleep, activity, and wellness data through the official Garmin Connect Personal API. It can run locally or be self-hosted on Cloudflare Workers for access from Claude and other MCP clients.

Connects a user's own Garmin data to compatible AI clients through Garmin's official Personal API, running locally over stdio with read-only access and no Garmin username or password.

Unofficial MCP server for Fitatu, the Polish calorie counter: read and log food, weight, water, body measurements and workouts, check calories and macros left, set goals and get weekly reports. 47 tools (26 read-only), read-only and demo modes, stdio or HTTP with a token, free and Premium accounts.

Enables ChatGPT and compatible AI clients to query read-only Garmin Connect data—including sleep, HRV, heart rate, Body Battery, wellness metrics, and activities—through a hosted OAuth-backed MCP connection using a personal API key.

Enables Claude to read your own Garmin Connect data—activities and exact pace splits, VO2 max and training effect, sleep, HRV, Body Battery, stress, weight and more—through Garmin's official Personal API, with no password or scraping. Access is read-only and runs entirely on your machine, so you can ask natural-language questions about training and recovery.

Enables local synchronization of Garmin activity and health data using a personal API key, then lets MCP-connected AI clients analyze training readiness and recovery with cited models and research. Supports viewing records, sleep/HRV, stress, Body Battery, and generating pre-run recommendations without hosting accounts or personal data.

Exposes Garmin Connect health and activity data (steps, sleep, heart rate, etc.) via MCP tools, with built-in login and MFA support.

Enables users to search and retrieve fitness exercise information from the Api Ninjas database. It supports filtering by exercise name, target muscle, type, and difficulty level.

Exposes 24 official Garmin personal API endpoints as MCP tools, letting users query daily health and wellness data (stress, steps, sleep, HRV, body battery, SpO2, activities) and download raw activity files for China or international regions. Data is returned as-is from Garmin's official client, with credential-based single-account setup.

Enables users to estimate VO2max from heart-rate ratios or Cooper 12-minute run distances, benchmark results against ACSM age and sex medians, and derive cardiorespiratory fitness biological age and all-cause mortality hazard ratios.

An MCP server that provides an interface to Google's Fitness API, enabling interaction with fitness data through natural language using the Multi-Agent Conversation Protocol.

Enables Claude to access and analyze Whoop health data including recovery, sleep, strain, and workouts through a custom MCP connector.

Enables MCP clients to query read-only Oura health data—readiness, sleep, HRV, activity, stress, heart rate and tags—through combined daily overviews, multi-day trends and aggregated heart-rate series. Authentication stays local via OAuth with PKCE, graceful handling of unavailable data types, and an optional sandbox of public sample data.

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

Provides local MCP tools to query your own Xiaomi Mi Fitness health data (sleep, workouts, heart rate, etc.) stored in a local SQLite database, enabling AI assistants to access personal health records without exposing credentials.

Ask your Oura Ring about sleep, readiness, activity, stress and heart rate in ChatGPT or Claude, in any language. Read-only, 10 task-oriented tools; runs in a sandbox demo mode with no credentials.

Enables AI assistants to read Technogym mywellness training history, including workout sessions, per-exercise set data, per-second exercise analytics, and heart-rate traces.

Provides read-only access to Oura ring biometrics via the Oura API, enabling Claude to query daily summaries, sleep, readiness, stress, workouts, baselines, and heart rate data. Designed to complement a Strava connector for joint analysis of training and recovery.

Exposes the Oura API v2 as an MCP server with tools to query all 19 data collections (e.g., sleep, heartrate) with automatic pagination and explicit truncation warnings.

Enables real-time Apple Watch heart rate monitoring via MCP tools, reading data from macOS HealthKit.

Query your Apple Health data including sleep, heart rate, steps, workouts, and more by ingesting an exported XML archive into a local SQLite database.

Enables LLM clients to read a user's locally-decrypted calisthenics training data and propose plan updates without direct mutations.

Enables Claude to query personal WHOOP health data including recovery, sleep, strain, workouts, and profile via WHOOP's OAuth 2.0 REST API.

This MCP server enables logging workouts in plain language through AI assistants and provides tracking of sessions, programs, records, estimated 1RM, and per-muscle load, with coaching informed by the user's logged data.

MCP server for the Google Health API: heart rate, activity, sleep, SpO2, HRV, ECG and irregular-rhythm notifications, read into a local SQLite cache for fast offline queries and trend analysis. OAuth 2.0 with automatic token refresh, incremental sync, a cache-only offline mode, and a doctor command that diagnoses a setup without spending quota.