"Automating HTTP API Wrapping into MCPT Tool" matching MCP servers:

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.

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.

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 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.

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.

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.

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

An MCP server that converts structured cycling workout specs into MyWhoosh .zwo and Garmin Connect workout files, with tools for validation, description, and rendering. It also includes skills for uploading workouts to both platforms.

MCP server that lets you ask questions about your Garmin training history in plain language. It ingests FIT files into DuckDB locally and exposes typed tools for analyzing activities, streams, and summaries.

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.

A stateless MCP server that normalizes strength training logs into a deterministic canonical schema, enabling consumers to build analytics downstream without storing data server-side.

Enables users to access their own Garmin Connect data through Garmin’s Personal API using their own API key, with ten tools covering all 26 endpoints plus passthrough access for future additions.

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

An MCP server that transforms Garmin data into compact, verdict-first coaching reports for LLMs, computing metrics like CTL/ATL/TSB and ACWR to answer training readiness questions.

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

Provides six deterministic, source-attributed hydration calculators (water intake, dehydration check, pregnancy intake, kidney-safe intake, athlete plan, energy optimization) as MCP tools, enabling AI clients to call them via stdio without custom HTTP coding.

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.

MCP server to read daily activity, sleep, heart rate, and body metrics from Google Health API, allowing AI assistants like Claude to access your health data. Optionally syncs health metrics to an Obsidian vault.

MCP server for the Oura Ring API v2, enabling natural language queries about sleep, readiness, activity, heart rate, and more.

Enables AI assistants to access and analyze Polar device health data, including exercises, heart rate, sleep, and recovery metrics, by preprocessing raw sensor data into compact summaries to avoid context window overload.

Brings Garmin training data into Claude via Intervals.icu, enabling querying of activities, wellness, and planned workouts, as well as creating structured workouts that sync back to the Garmin watch.

Aggregates and analyzes fitness data from multiple sources like Whoop and Strava through a modular adapter architecture. It enables users to monitor health metrics, track activities, and gain insights into sleep, recovery, and training performance.

Archives Garmin Connect health data locally (steps, HR, sleep, body battery) as JSON, no cloud, and also pulls context data (weather, pollen, air quality). Built-in MCP server (with SQLite cache) exposes the archive for querying via LLM tool calls.

A read-only MCP server for the WHOOP API v2 that lets you query and analyze your own recovery, sleep, strain, cycles, and workout data. Note: currently a pre-alpha scaffold with stubbed internals.

Enables AI agents to sync WHOOP recovery, sleep, workouts, cycles, and body-measurement data into a local Postgres database and query it through fast, offline-capable MCP tools without repeatedly hitting WHOOP API rate limits.

Gives Claude access to your WHOOP health data including recovery, sleep, workouts, cycles, body measurements, and profile via the WHOOP Developer API.

This server enables advanced personal health coaching by transforming raw Garmin Connect telemetry into structured data for AI analysis and decision-making. It provides deep workout debriefing, tracks longitudinal training loads, and generates structured, periodized workout plans.

An MCP server that exposes the Hevy fitness API as 22 tools, enabling AI agents to manage workouts, routines, exercise templates, and body measurements through natural language.

MCP server for the Oura Ring API v2, providing access to sleep, activity, readiness, heart rate, and workout data via OAuth.

This server lets Claude, Cursor, or any MCP client read a user's own health and fitness data through 26 read-only tools for activities, sleep, HRV, Body Battery, stress, steps, heart rate, weight, nutrition, and women's health. It connects via the official Personal API and can be self-hosted for free on Vercel.

An MCP server and CLI for logging food to Lose It!, enabling food search, diary management, meal logging, and weight recording via unofficial API.

Enables MCP-capable AI apps to query a user's own Garmin sleep, HRV, stress, Body Battery, heart-rate, activity, and body-metric data through Garmin's official Personal API in a read-only, locally run setup.

Enables MCP clients to read a user's own Garmin data—including activities, sleep, HRV, Body Battery, stress, steps, heart rate, weight, and more—through 26 read-only tools backed by Garmin's Personal API.

Enables read-only querying of your own Garmin Connect data — sleep, HRV, resting HR, Body Battery, activities, training volume, body composition, and nutrition — through Garmin's official Personal API using a revocable key. Returns compact, unit-labelled JSON shaped around questions so whole date ranges fit in context.