"Creating an MCP Server Using an API" matching MCP servers:

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

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.

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.

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

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.

An MCP server that lets Claude plan cycling training in intervals.icu, upload workouts to the calendar, and review planned versus actual outcomes, fitness trends, and power curves.

Query Apple Health export data with an LLM via a semantic layer that avoids common data traps, enabling accurate natural-language queries about health metrics. Optionally imports CPAP therapy data for correlation.

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.

Provides read-only access to your Garmin Connect health data, including sleep, HRV, body battery, stress, training readiness, and activities, through an MCP server.

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.

Enables an LLM to search a movement library, log single-movement and multi-movement workout results, and pull complete logged training history plus PR trends for Beyond the Whiteboard straight from a chat. All logged entries are posted privately, and session authentication can refresh automatically.

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 an agent to fetch one night of Eight Sleep data as ready-made text — scores, sleep stages, HRV, heart and respiratory rate versus your averages, and bed/room temperatures — plus short summaries of earlier nights for a morning check-in. Read-only, so nothing on the mattress can be changed.

Enables read-only access to RENPHO Health smart scale measurements through MCP, allowing users to retrieve latest readings, body composition history, and weight trends via an MCP client.

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.

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.

MCP server for reading and querying Garmin Connect data, including activities, strength history, recovery, trends, and optionally creating workouts.

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.